Systems and methods for communicating transaction data between mobile devices

ABSTRACT

Provided is a computer-implemented method for communicating transaction data between mobile devices, including: registering account data associated with a merchant account corresponding to short message service (SMS) device data associated with a point-of-sale (POS) device, and account data associated with a user account as corresponding to SMS device data associated with a user device; receiving, via an SMS communication connection, transaction data associated with a transaction from the POS device, verifying the POS device and the user device are registered; in response to determining that an account balance of the user account is greater than the transaction authorization limit, transmitting a first confirmation message associated with the transaction, via an SMS communication connection, to the user device to confirm the transaction; and in response to receiving a first confirmation response associated with the transaction, via an SMS communication connection, processing the transaction data.

CROSS-REFERENCE TO RELATED APPLICATION

This application is the United States national phase of InternationalApplication No. PCT/US2019/041164 filed Jul. 10, 2019, the entiredisclosure of which is hereby incorporated by reference in its entirety.

BACKGROUND 1. Technical Field

This disclosure relates generally to transaction processing and, in somenon-limiting aspects or embodiments, to systems, methods, and computerprogram products for communicating transaction data between mobiledevices.

2. Technical Considerations

Mobile point-of-sale (POS) systems have been developed to enableindividuals to process payment transactions. For example, mobile POSsystems may connect to mobile devices such as tablets or smartphonesthat are configured to communicate information to and from the internetvia wired or wireless data connections (e.g., Wi-Fi®, third-generation(3G) mobile networks, fourth-generation (4G) mobile networks, and/or thelike). Such mobile POS systems may read information from credit cards ordebit cards and, in response, communicate such information, along withother transaction-specific data, via the wired or wireless dataconnections to a remote system for processing.

However, similar to traditional POS systems, once the mobile POS systemsread the information from the credit or debit cards, the transaction maybe finalized by having the buyer in possession of the credit or debitcard engage the mobile device to input additionally-requestedinformation (e.g., a personal identification number (PIN) and/or asignature). As a result, communication with the buyer, particularly viathe mobile device, may be limited once payment information iscommunicated to the POS terminal. Parties such as transaction serviceproviders, issuer institutions, and acquirer institutions, in turn, mayrely on only the information received at the mobile POS terminal whilethe buyer is present to verify the accuracy of the credit or debit cardinformation. This reliance may lead to increases in transactionprocessing time, both at the POS terminal (when waiting for additionalinput from the user) and while the transaction is being processed by thetransaction service provider.

SUMMARY

Accordingly, provided are improved systems, devices, products,apparatus, and/or methods for communicating transaction data betweenmobile devices.

According to non-limiting aspects or embodiments, provided is acomputer-implemented method for communicating transaction data betweenmobile devices that may include registering, with at least oneprocessor, account data associated with a merchant account ascorresponding to short message service (SMS) device data associated witha point-of-sale (POS) device; registering, with at least one processor,account data associated with a user account as corresponding to SMSdevice data associated with a user device; receiving, with at least oneprocessor via an SMS communication connection, transaction dataassociated with a transaction from the POS device, comprising: the SMSdevice data associated with the POS device, the SMS device dataassociated with the user device, and parameter data associated with thetransaction, the transaction initiated by the POS device, the parameterdata comprising a transaction value, verifying, with at least oneprocessor, that the POS device and the user device are registered; basedon determining, with at least one processor, that an account balance ofthe user account is greater than the transaction value, transmitting,with at least one processor, a first confirmation message associatedwith the transaction, via an SMS communication connection, to the userdevice to confirm the transaction; and based on receiving, with at leastone processor, a first confirmation response message associated with thetransaction from the user device via an SMS communication connection,processing, with at least one processor, the transaction data.

In some non-limiting aspects or embodiments, computer implementedmethods may include, based on determining that the transactionauthorization limit is greater than an authorization limit threshold,transmitting, with at least one processor, a second confirmation messageassociated with the transaction to the user device; and based onreceiving a second confirmation response message associated with thetransaction, confirming, with at least one processor and prior toprocessing the transaction data, that the second confirmation responseis valid.

According to some non-limiting aspects or embodiments, registeringaccount data associated with the account as corresponding to SMS devicedata associated with the user device may include registering, with atleast one processor, confirmation data associated with confirmation ofthe transaction, the confirmation data corresponding to the SMS devicedata associated with a user device.

In some non-limiting aspects or embodiments, computer-implementedmethods may include, determining, with at least one processor, that thesecond confirmation response message indicates that the transaction isvalid based on a comparison of the second confirmation response messageto the confirmation data received during registration of the accountdata associated with the account corresponding to the SMS device dataassociated with a user device.

According to some non-limiting aspects or embodiments, verifying the POSdevice and the user device are registered may include determining, withat least one processor, that the SMS device data associated with the POSdevice corresponds to the account data associated with a merchantaccount; and determining, with at least one processor, that the SMSdevice data associated with the user device corresponds to the accountdata associated with a user account.

In some non-limiting aspects or embodiments, computer implementedmethods may include, based on receiving the transaction data associatedwith the transaction, transmitting, with at least one processor, atransaction parameter confirmation message; and based on receivingtransaction parameter confirmation response message indicating that thetransaction is authorized, transmitting, with at least one processor, apre-authorization message associated with the transaction.

According to some non-limiting aspects or embodiments, computerimplemented methods may include, based on receiving the transaction dataassociated with the transaction, transmitting, with at least oneprocessor, a pre-authorization request message associated with thetransaction; and based on receiving a pre-authorization response messageassociated with the transaction indicating the transaction is notauthorized, transmitting, with at least one processor, a messageassociated with the transaction to the POS device, the messageindicating that the transaction was not authorized.

In some non-limiting aspects or embodiments, verifying the POS deviceand the user device are registered may include, based on determiningthat at least one of the POS device and the user device are notregistered, transmitting, with at least one processor, a messageassociated with the transaction to the at least one of the POS deviceand the user device indicating that the at least one of the POS deviceand the user device are not registered.

According to non-limiting aspects or embodiments, provided is a systemfor communicating transaction data between mobile devices that mayinclude at least one processor programmed or configured to registeraccount data associated with a merchant account as corresponding toshort message service (SMS) device data associated with a point-of-sale(POS) device; register account data associated with a user account ascorresponding to SMS device data associated with a user device; receive,via an SMS communication connection, transaction data associated with atransaction from the POS device, comprising: the SMS device dataassociated with the POS device, the SMS device data associated with theuser device, and parameter data associated with the transaction, thetransaction initiated by the POS device, the parameter data comprising atransaction value, verify that the POS device and the user device areregistered; based on determining, with at least one processor, that anaccount balance of the user account is greater than the transactionvalue, transmitting, with at least one processor, a first confirmationmessage associated with the transaction, via an SMS communicationconnection, to the user device to confirm the transaction; and based onreceiving, with at least one processor, a first confirmation responsemessage associated with the transaction from the user device via an SMScommunication connection, processing, with at least one processor, thetransaction data.

In some non-limiting aspects or embodiments, the at least one processormay be further programmed or configured to, based on determining thatthe transaction authorization limit is greater than an authorizationlimit threshold, transmit a second confirmation message associated withthe transaction to the user device; and based on receiving a secondconfirmation response message associated with the transaction, confirm,prior to processing the transaction data, that the second confirmationresponse is valid.

According to some non-limiting aspects or embodiments, when registeringaccount data associated with the account as corresponding to SMS devicedata associated with the user device, the at least one processor may beprogrammed or configured to register confirmation data associated withconfirmation of the transaction, the confirmation data corresponding tothe SMS device data associated with a user device.

In some non-limiting aspects or embodiments, the at least one processormay be further programmed or configured to determine that the secondconfirmation response message indicates that the transaction is validbased on a comparison of the second confirmation response message to theconfirmation data received during registration of the account dataassociated with the account corresponding to the SMS device dataassociated with a user device.

According to some non-limiting aspects or embodiments, the at least oneprocessor may be further programmed or configured to: determine that theSMS device data associated with the POS device corresponds to theaccount data associated with a merchant account; and determine that theSMS device data associated with the user device corresponds to theaccount data associated with a user account.

In some non-limiting aspects or embodiments, the at least one processormay be further programmed or configured to, based on receiving thetransaction data associated with the transaction, transmit a transactionparameter confirmation message; and based on receiving transactionparameter confirmation response message indicating that the transactionis authorized, transmit a pre-authorization message associated with thetransaction.

According to some non-limiting aspects or embodiments, the at least oneprocessor may be further programmed or configured to, based on receivingthe transaction data associated with the transaction, transmit apre-authorization request message associated with the transaction; andin response to receiving a pre-authorization response message associatedwith the transaction indicating the transaction is not authorized,transmit a message associated with the transaction to the POS device,the message indicating that the transaction was not authorized.

In some non-limiting aspects or embodiments, when verifying the POSdevice and the user device are registered, the at least one processormay be programmed or configured to: based on determining that at leastone of the POS device and the user device are not registered, transmit amessage associated with the transaction to the at least one of the POSdevice and the user device indicating that the at least one of the POSdevice and the user device are not registered

According to non-limiting aspects or embodiments, provided is acomputer-program product for communicating transaction data betweenmobile devices, the computer program product comprising at least onenon-transitory computer-readable medium comprising one or moreinstructions that, when executed by at least one processor, cause the atleast one processor to: register account data associated with a merchantaccount as corresponding to short message service (SMS) device dataassociated with a point-of-sale (POS) device; register account dataassociated with a user account as corresponding to SMS device dataassociated with a user device; receive, via an SMS communicationconnection, transaction data associated with a transaction from the POSdevice, comprising: the SMS device data associated with the POS device,the SMS device data associated with the user device, and parameter dataassociated with the transaction, the transaction initiated by the POSdevice, the parameter data comprising a transaction value, verify thatthe POS device and the user device are registered; based on determining,with at least one processor, that an account balance of the user accountis greater than the transaction value, transmitting, with at least oneprocessor, a first confirmation message associated with the transaction,via an SMS communication connection, to the user device to confirm thetransaction; and based on receiving, with at least one processor, afirst confirmation response message associated with the transaction fromthe user device via an SMS communication connection, processing, with atleast one processor, the transaction data.

In some non-limiting aspects or embodiments, the one or moreinstructions may further cause the at least one processor to, based ondetermining that the transaction authorization limit is greater than anauthorization limit threshold, transmit a second confirmation messageassociated with the transaction to the user device; and based onreceiving a second confirmation response message associated with thetransaction, confirm, prior to processing the transaction data, that thesecond confirmation response is valid.

According to some non-limiting aspects or embodiments, the one or moreinstructions that cause the at least one processor to register accountdata associated with the account as corresponding to SMS device dataassociated with the user device cause the at least one processor to:register confirmation data associated with confirmation of thetransaction, the confirmation data corresponding to the SMS device dataassociated with a user device.

In some non-limiting aspects or embodiments, the one or moreinstructions may further cause the at least one processor to: determinethat the second confirmation response message indicates that thetransaction is valid based on a comparison of the second confirmationresponse message to the confirmation data received during registrationof the account data associated with the account corresponding to the SMSdevice data associated with a user device.

According to some non-limiting aspects or embodiments, the one or moreinstructions that cause the at least one processor to verify that thePOS device and the user device are registered may cause the at least oneprocessor to determine that the SMS device data associated with the POSdevice corresponds to the account data associated with a merchantaccount; and determine that the SMS device data associated with the userdevice corresponds to the account data associated with a user account.

In some non-limiting aspects or embodiments, the one or moreinstructions may further cause the at least one processor to, based onreceiving the transaction data associated with the transaction, transmita transaction parameter confirmation message; and based on receivingtransaction parameter confirmation response message indicating that thetransaction is authorized, transmit a pre-authorization messageassociated with the transaction.

According to some non-limiting aspects or embodiments, the one or moreinstructions may further cause the at least one processor to, based onreceiving the transaction data associated with the transaction, transmita pre-authorization request message associated with the transaction; andin response to receiving a pre-authorization response message associatedwith the transaction indicating the transaction is not authorized,transmit a message associated with the transaction to the POS device,the message indicating that the transaction was not authorized.

In some non-limiting aspects or embodiments, the one or moreinstructions that cause the at least one processor to verify that thePOS device and the user device are registered may cause the at least oneprocessor to, based on determining that at least one of the POS deviceand the user device are not registered, transmit a message associatedwith the transaction to the at least one of the POS device and the userdevice indicating that the at least one of the POS device and the userdevice are not registered.

Further non-limiting aspects or embodiments are set forth in thefollowing numbered clauses:

Clause 1: A computer-implemented method for communicating transactiondata between mobile devices, the computer-implemented method comprising:registering, with at least one processor, account data associated with amerchant account as corresponding to short message service (SMS) devicedata associated with a point-of-sale (POS) device; registering, with atleast one processor, account data associated with a user account ascorresponding to SMS device data associated with a user device;receiving, with at least one processor via an SMS communicationconnection, transaction data associated with a transaction from the POSdevice, comprising: the SMS device data associated with the POS device,the SMS device data associated with the user device, and parameter dataassociated with the transaction, the transaction initiated by the POSdevice, the parameter data comprising a transaction value, verifying,with at least one processor, that the POS device and the user device areregistered; based on determining, with at least one processor, that anaccount balance of the user account is greater than the transactionvalue, transmitting, with at least one processor, a first confirmationmessage associated with the transaction, via an SMS communicationconnection, to the user device to confirm the transaction; and based onreceiving, with at least one processor, a first confirmation responsemessage associated with the transaction from the user device via an SMScommunication connection, processing, with at least one processor, thetransaction data.

Clause 2: The computer-implemented method according to clause 1, furthercomprising: based on determining that the transaction authorizationlimit is greater than an authorization limit threshold, transmitting,with at least one processor, a second confirmation message associatedwith the transaction to the user device; and based on receiving a secondconfirmation response message associated with the transaction,confirming, with at least one processor and prior to processing thetransaction data, that the second confirmation response is valid.

Clause 3: The computer-implemented method according to clauses 1 or 2,wherein registering account data associated with the account ascorresponding to SMS device data associated with the user device furthercomprises: registering, with at least one processor, confirmation dataassociated with confirmation of the transaction, the confirmation datacorresponding to the SMS device data associated with a user device.

Clause 4: The computer-implemented method according to any of clauses1-3, further comprising: determining, with at least one processor, thatthe second confirmation response message indicates that the transactionis valid based on a comparison of the second confirmation responsemessage to the confirmation data received during registration of theaccount data associated with the account corresponding to the SMS devicedata associated with a user device.

Clause 5: The computer-implemented method according to any of clauses1-4, wherein verifying the POS device and the user device are registeredfurther comprises: determining, with at least one processor, that theSMS device data associated with the POS device corresponds to theaccount data associated with a merchant account; and determining, withat least one processor, that the SMS device data associated with theuser device corresponds to the account data associated with a useraccount.

Clause 6: The computer-implemented method according to any of clauses1-5, further comprising: based on receiving the transaction dataassociated with the transaction, transmitting, with at least oneprocessor, a transaction parameter confirmation message; and based onreceiving transaction parameter confirmation response message indicatingthat the transaction is authorized, transmitting, with at least oneprocessor, a pre-authorization message associated with the transaction.

Clause 7: The computer-implemented method according to any of clauses1-6, further comprising: based on receiving the transaction dataassociated with the transaction, transmitting, with at least oneprocessor, a pre-authorization request message associated with thetransaction; and in response to receiving a pre-authorization responsemessage associated with the transaction indicating the transaction isnot authorized, transmitting, with at least one processor, a messageassociated with the transaction to the POS device, the messageindicating that the transaction was not authorized.

Clause 8: The computer-implemented method according to any of clauses1-7, wherein verifying the POS device and the user device are registeredfurther comprises: based on determining that at least one of the POSdevice and the user device are not registered, transmitting, with atleast one processor, a message associated with the transaction to the atleast one of the POS device and the user device indicating that the atleast one of the POS device and the user device are not registered.

Clause 9: A system for communicating transaction data between mobiledevices, the system comprising: at least one processor programmed orconfigured to: register account data associated with a merchant accountas corresponding to short message service (SMS) device data associatedwith a point-of-sale (POS) device; register account data associated witha user account as corresponding to SMS device data associated with auser device; receive, via an SMS communication connection, transactiondata associated with a transaction from the POS device, comprising: theSMS device data associated with the POS device, the SMS device dataassociated with the user device, and parameter data associated with thetransaction, the transaction initiated by the POS device, the parameterdata comprising a transaction value, verify that the POS device and theuser device are registered; based on determining, with at least oneprocessor, that an account balance of the user account is greater thanthe transaction value, transmitting, with at least one processor, afirst confirmation message associated with the transaction, via an SMScommunication connection, to the user device to confirm the transaction;and based on receiving, with at least one processor, a firstconfirmation response message associated with the transaction from theuser device via an SMS communication connection, processing, with atleast one processor, the transaction data.

Clause 10: The system according to clause 9, wherein the at least oneprocessor is further programmed or configured to: based on determiningthat the transaction authorization limit is greater than anauthorization limit threshold, transmit a second confirmation messageassociated with the transaction to the user device; and based onreceiving a second confirmation response message associated with thetransaction, confirm, prior to processing the transaction data, that thesecond confirmation response is valid.

Clause 11: The system according to clauses 9 or 10, wherein, whenregistering account data associated with the account as corresponding toSMS device data associated with the user device, the at least oneprocessor is programmed or configured to: register confirmation dataassociated with confirmation of the transaction, the confirmation datacorresponding to the SMS device data associated with a user device.

Clause 12: The system according to any of clauses 9-11, wherein the atleast one processor is further programmed or configured to: determinethat the second confirmation response message indicates that thetransaction is valid based on a comparison of the second confirmationresponse message to the confirmation data received during registrationof the account data associated with the account corresponding to the SMSdevice data associated with a user device.

Clause 13: The system according to any of clauses 9-12, wherein, whenverifying the POS device and the user device are registered, the atleast one processor is programmed or configured to: determine that theSMS device data associated with the POS device corresponds to theaccount data associated with a merchant account; and determine that theSMS device data associated with the user device corresponds to theaccount data associated with a user account.

Clause 14: The system according to any of clauses 9-13, wherein the atleast one processor is further programmed or configured to: based onreceiving the transaction data associated with the transaction, transmita transaction parameter confirmation message; and based on receivingtransaction parameter confirmation response message indicating that thetransaction is authorized, transmit a pre-authorization messageassociated with the transaction.

Clause 15: The system according to any of clauses 9-14, wherein the atleast one processor is further programmed or configured to: based onreceiving the transaction data associated with the transaction, transmita pre-authorization request message associated with the transaction; andin response to receiving a pre-authorization response message associatedwith the transaction indicating the transaction is not authorized,transmit a message associated with the transaction to the POS device,the message indicating that the transaction was not authorized.

Clause 16: The system according to any of clauses 9-15, wherein, whenverifying the POS device and the user device are registered, the atleast one processor is programmed or configured to: based on determiningthat at least one of the POS device and the user device are notregistered, transmit a message associated with the transaction to the atleast one of the POS device and the user device indicating that the atleast one of the POS device and the user device are not registered.

Clause 17: A computer-program product for communicating transaction databetween mobile devices, the computer program product comprising at leastone non-transitory computer-readable medium comprising one or moreinstructions that, when executed by at least one processor, cause the atleast one processor to: register account data associated with a merchantaccount as corresponding to short message service (SMS) device dataassociated with a point-of-sale (POS) device; register account dataassociated with a user account as corresponding to SMS device dataassociated with a user device; receive, via an SMS communicationconnection, transaction data associated with a transaction from the POSdevice, comprising: the SMS device data associated with the POS device,the SMS device data associated with the user device, and parameter dataassociated with the transaction, the transaction initiated by the POSdevice, the parameter data comprising a transaction value, verify thatthe POS device and the user device are registered; based on determining,with at least one processor, that an account balance of the user accountis greater than the transaction value, transmitting, with at least oneprocessor, a first confirmation message associated with the transaction,via an SMS communication connection, to the user device to confirm thetransaction; and based on receiving, with at least one processor, afirst confirmation response message associated with the transaction fromthe user device via an SMS communication connection, processing, with atleast one processor, the transaction data.

Clause 18: The computer program product according to clause 17, whereinthe one or more instructions further cause the at least one processorto: based on determining that the transaction authorization limit isgreater than an authorization limit threshold, transmit a secondconfirmation message associated with the transaction to the user device;and based on receiving a second confirmation response message associatedwith the transaction, confirm, prior to processing the transaction data,that the second confirmation response is valid.

Clause 19: The computer program product according to clauses 17 or 18,wherein the one or more instructions that cause the at least oneprocessor to register account data associated with the account ascorresponding to SMS device data associated with the user device causethe at least one processor to: register confirmation data associatedwith confirmation of the transaction, the confirmation datacorresponding to the SMS device data associated with a user device.

Clause 20: The computer program product according to any of clauses17-19, wherein the one or more instructions further cause the at leastone processor to: determine that the second confirmation responsemessage indicates that the transaction is valid based on a comparison ofthe second confirmation response message to the confirmation datareceived during registration of the account data associated with theaccount corresponding to the SMS device data associated with a userdevice.

Clause 21: The computer program product according to any of clauses17-20, wherein the one or more instructions that cause the at least oneprocessor to verify that the POS device and the user device areregistered cause the at least one processor to: determine that the SMSdevice data associated with the POS device corresponds to the accountdata associated with a merchant account; and determine that the SMSdevice data associated with the user device corresponds to the accountdata associated with a user account.

Clause 22: The computer program product according to any of clauses17-21, wherein the one or more instructions further cause the at leastone processor to: based on receiving the transaction data associatedwith the transaction, transmit a transaction parameter confirmationmessage; and based on receiving transaction parameter confirmationresponse message indicating that the transaction is authorized, transmita pre-authorization message associated with the transaction.

Clause 23: The computer program product according to any of clauses17-22, wherein the one or more instructions further cause the at leastone processor to: based on receiving the transaction data associatedwith the transaction, transmit a pre-authorization request messageassociated with the transaction; and in response to receiving apre-authorization response message associated with the transactionindicating the transaction is not authorized, transmit a messageassociated with the transaction to the POS device, the messageindicating that the transaction was not authorized.

Clause 24: The computer program product according to any of clauses17-23, wherein the one or more instructions that cause the at least oneprocessor to verify that the POS device and the user device areregistered cause the at least one processor to: based on determiningthat at least one of the POS device and the user device are notregistered, transmit a message associated with the transaction to the atleast one of the POS device and the user device indicating that the atleast one of the POS device and the user device are not registered.

Clause 25: A computer-implemented method for communicating transactiondata between mobile devices, the computer-implemented method comprising:registering, with at least one processor, account data associated with amerchant account as corresponding to device data associated with amobile point-of-sale (POS) device; registering, with at least oneprocessor, account data associated with a user account as correspondingto electronic wallet device data associated with a user device;receiving, with at least one processor via a data connection,transaction data associated with a transaction from the POS device,comprising: the device data associated with the POS device, theelectronic wallet device data associated with the user device, andparameter data associated with the transaction, the transactioninitiated by the POS device, the parameter data comprising a transactionvalue, verifying, with at least one processor, that the POS device andthe user device are registered; based on determining, with at least oneprocessor, that an account balance of the user account is greater thanthe transaction value, transmitting, with at least one processor, afirst confirmation message associated with the transaction, via a dataconnection, to the user device to confirm the transaction; and based onreceiving, with at least one processor, a first confirmation responsemessage associated with the transaction from the user device via a dataconnection, processing, with at least one processor, the transactiondata.

Clause 26: The computer-implemented method according to clause 25,further comprising: based on determining that the transaction value isgreater than an authorization limit threshold, transmitting, with atleast one processor, a second confirmation message associated with thetransaction to the user device; and based on receiving a secondconfirmation response message associated with the transaction,confirming, with at least one processor and prior to processing thetransaction data, that the second confirmation response is valid.

Clause 27: The computer-implemented method according to clauses 25 or26, wherein registering account data associated with the account ascorresponding to electronic wallet device data associated with the userdevice further comprises: registering, with at least one processor,confirmation data associated with confirmation of the transaction, theconfirmation data corresponding to the electronic wallet device dataassociated with a user device.

Clause 28: The computer-implemented method according to any of clauses25-27, further comprising: determining, with at least one processor,that the second confirmation response message indicates that thetransaction is valid based on a comparison of the second confirmationresponse message to the confirmation data received during registrationof the account data associated with the account corresponding to theelectronic wallet device data associated with a user device.

Clause 29: The computer-implemented method according to any of clauses25-28, wherein verifying the POS device and the user device areregistered further comprises: determining, with at least one processor,that the electronic wallet device data associated with the POS devicecorresponds to the account data associated with a merchant account; anddetermining, with at least one processor, that the electronic walletdevice data associated with the user device corresponds to the accountdata associated with a user account.

Clause 30: The computer-implemented method according to any of clauses25-29, further comprising: based on receiving the transaction dataassociated with the transaction, transmitting, with at least oneprocessor, a transaction parameter confirmation message; and based onreceiving transaction parameter confirmation response message indicatingthat the transaction is authorized, transmitting, with at least oneprocessor, a pre-authorization message associated with the transaction.

Clause 31: The computer-implemented method according to any of clauses25-30, further comprising: based on receiving the transaction dataassociated with the transaction, transmitting, with at least oneprocessor, a pre-authorization request message associated with thetransaction; and in response to receiving a pre-authorization responsemessage associated with the transaction indicating the transaction isnot authorized, transmitting, with at least one processor, a messageassociated with the transaction to the POS device, the messageindicating that the transaction was not authorized.

Clause 32: The computer-implemented method according to any of clauses25-31, wherein verifying the POS device and the user device areregistered further comprises: based on determining that at least one ofthe POS device and the user device are not registered, transmitting,with at least one processor, a message associated with the transactionto the at least one of the POS device and the user device indicatingthat the at least one of the POS device and the user device are notregistered.

Clause 33. A system for communicating transaction data between mobiledevices, the system comprising: at least one processor programmed orconfigured to: register account data associated with a merchant accountas corresponding to device data associated with a mobile point-of-sale(POS) device; register account data associated with a user account ascorresponding to electronic wallet device data associated with a userdevice; receive, via data connection, transaction data associated with atransaction from the POS device, comprising: the device data associatedwith the POS device, the electronic wallet device data associated withthe user device, and parameter data associated with the transaction, thetransaction initiated by the POS device, the parameter data comprising atransaction value, verify that the POS device and the user device areregistered; based on determining that an account balance of the useraccount is greater than the transaction value, transmit a firstconfirmation message associated with the transaction, via a dataconnection, to the user device to confirm the transaction; and based onreceiving a first confirmation response message associated with thetransaction from the user device via a data connection, process thetransaction data.

Clause 34: The system according to clause 33, wherein the at least oneprocessor is further programmed or configured to: based on determiningthat the transaction value is greater than an authorization limitthreshold, transmit a second confirmation message associated with thetransaction to the user device; and based on receiving a secondconfirmation response message associated with the transaction, confirm,prior to processing the transaction data, that the second confirmationresponse is valid.

Clause 35: The system according to clauses 33 or 34, wherein, whenregistering account data associated with the account as corresponding toelectronic wallet device data associated with the user device the atleast one processor is programmed or configured to: registerconfirmation data associated with confirmation of the transaction, theconfirmation data corresponding to the electronic wallet device dataassociated with a user device.

Clause 36: The system according to any of clauses 33-35, wherein the atleast one processor is further programmed or configured to: determinethat the second confirmation response message indicates that thetransaction is valid based on a comparison of the second confirmationresponse message to the confirmation data received during registrationof the account data associated with the account corresponding to theelectronic wallet device data associated with a user device.

Clause 37: The system according to any of clauses 33-36, wherein, whenverifying the POS device and the user device are registered, the atleast one processor is programmed or configured to: determine that theelectronic wallet device data associated with the POS device correspondsto the account data associated with a merchant account; and determinethat the electronic wallet device data associated with the user devicecorresponds to the account data associated with a user account.

Clause 38: The system according to any of clauses 33-37, wherein the atleast one processor is further programmed or configured to: based onreceiving the transaction data associated with the transaction, transmita transaction parameter confirmation message; and based on receivingtransaction parameter confirmation response message indicating that thetransaction is authorized, transmit a pre-authorization messageassociated with the transaction.

Clause 39: The system according to any of clauses 33-38, wherein the atleast one processor is further programmed or configured to: based onreceiving the transaction data associated with the transaction, transmita pre-authorization request message associated with the transaction; andin response to receiving a pre-authorization response message associatedwith the transaction indicating the transaction is not authorized,transmit a message associated with the transaction to the POS device,the message indicating that the transaction was not authorized.

Clause 40: The system according to any of clauses 33-39, wherein, whenverifying the POS device and the user device are registered, the atleast one processor is programmed or configured to: based on determiningthat at least one of the POS device and the user device are notregistered, transmit a message associated with the transaction to the atleast one of the POS device and the user device indicating that the atleast one of the POS device and the user device are not registered.

Clause 41: A computer-program product for communicating transaction databetween mobile devices, the computer program product comprising at leastone non-transitory computer-readable medium comprising one or moreinstructions that, when executed by at least one processor, cause the atleast one processor to: register account data associated with a merchantaccount as corresponding to device data associated with a mobilepoint-of-sale (POS) device; register account data associated with a useraccount as corresponding to electronic wallet device data associatedwith a user device; receive, via data connection, transaction dataassociated with a transaction from the POS device, comprising: thedevice data associated with the POS device, the electronic wallet devicedata associated with the user device, and parameter data associated withthe transaction, the transaction initiated by the POS device, theparameter data comprising a transaction value, verify that the POSdevice and the user device are registered; based on determining that anaccount balance of the user account is greater than the transactionvalue, transmit a first confirmation message associated with thetransaction, via a data connection, to the user device to confirm thetransaction; and based on receiving a first confirmation responsemessage associated with the transaction from the user device via a dataconnection, process the transaction data.

Clause 42: The computer-program product according to clause 41, whereinthe one or more instructions further cause the at least one processorto: based on determining that the transaction value is greater than anauthorization limit threshold, transmit a second confirmation messageassociated with the transaction to the user device; and based onreceiving a second confirmation response message associated with thetransaction, confirm, prior to processing the transaction data, that thesecond confirmation response is valid.

Clause 43: The computer-program product according to clauses 41 or 42,wherein the one or more instructions that cause the at least oneprocessor to register account data associated with the account ascorresponding to electronic wallet device data associated with the userdevice cause the at least one processor to: register confirmation dataassociated with confirmation of the transaction, the confirmation datacorresponding to the electronic wallet device data associated with auser device.

Clause 44: The computer-program product according to any of clauses41-43, wherein the one or more instructions further cause the at leastone processor to: determine that the second confirmation responsemessage indicates that the transaction is valid based on a comparison ofthe second confirmation response message to the confirmation datareceived during registration of the account data associated with theaccount corresponding to the electronic wallet device data associatedwith a user device.

Clause 45: The computer-program product according to any of clauses41-44, wherein the one or more instructions that cause the at least oneprocessor to verify that the POS device and the user device areregistered cause the at least one processor to: determine that theelectronic wallet device data associated with the POS device correspondsto the account data associated with a merchant account; and determinethat the electronic wallet device data associated with the user devicecorresponds to the account data associated with a user account.

Clause 46: The computer-program product according to any of clauses41-45, wherein the one or more instructions further cause the at leastone processor to: based on receiving the transaction data associatedwith the transaction, transmit a transaction parameter confirmationmessage; and based on receiving transaction parameter confirmationresponse message indicating that the transaction is authorized, transmita pre-authorization message associated with the transaction.

Clause 47: The computer-program product according to any of clauses41-46, wherein the one or more instructions further cause the at leastone processor to: based on receiving the transaction data associatedwith the transaction, transmit a pre-authorization request messageassociated with the transaction; and in response to receiving apre-authorization response message associated with the transactionindicating the transaction is not authorized, transmit a messageassociated with the transaction to the POS device, the messageindicating that the transaction was not authorized.

Clause 48: The computer-program product according to any of clauses41-47, wherein the one or more instructions that cause the at least oneprocessor to verify the POS device and the user device are registeredcause the at least one processor to: based on determining that at leastone of the POS device and the user device are not registered, transmit amessage associated with the transaction to the at least one of the POSdevice and the user device indicating that the at least one of the POSdevice and the user device are not registered.

These and other features and characteristics of the present disclosure,as well as the methods of operation and functions of the relatedelements of structures and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the disclosure. Asused in the specification and the claims, the singular form of “a”,“an”, and “the” include plural referents unless the context clearlydictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

Additional advantages and details of the present disclosure areexplained in greater detail below with reference to the exemplaryembodiments that are illustrated in the accompanying schematic figures,in which:

FIG. 1 is a diagram of non-limiting aspects or embodiments of a systemfor communicating transaction data between mobile devices;

FIG. 2 is a diagram of non-limiting aspects or embodiments of componentsof one or more devices illustrated by FIG. 1 ;

FIGS. 3A and 3B are flow diagrams of a process for communicatingtransaction data between mobile devices;

FIG. 4 is a diagram of an implementation of non-limiting aspects orembodiments of the process shown in FIGS. 3A and 3B;

FIGS. 5A and 5B are diagrams of an implementation of non-limitingaspects or embodiments of the process shown in FIGS. 3A and 3B; and

FIGS. 6A and 6B are diagrams of an implementation of non-limitingaspects or embodiments of the process shown in FIGS. 3A and 3B.

DETAILED DESCRIPTION

For purposes of the description hereinafter, the terms “end,” “upper,”“lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,”“lateral,” “longitudinal,” and derivatives thereof shall relate to thedisclosure as it is oriented in the drawing figures. However, it is tobe understood that the disclosure may assume various alternativevariations and step sequences, except where expressly specified to thecontrary. It is also to be understood that the specific devices andprocesses illustrated in the attached drawings, and described in thefollowing specification, are simply exemplary embodiments or aspects ofthe disclosure. Hence, specific dimensions and other physicalcharacteristics related to the embodiments or aspects of the embodimentsdisclosed herein are not to be considered as limiting unless otherwiseindicated.

No aspect, component, element, structure, act, step, function,instruction, and/or the like used herein should be construed as criticalor essential unless explicitly described as such. In addition, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more” and “at leastone.” Furthermore, as used herein, the term “set” is intended to includeone or more items (e.g., related items, unrelated items, a combinationof related and unrelated items, etc.) and may be used interchangeablywith “one or more” or “at least one.” Where only one item is intended,the term “one” or similar language is used. Also, as used herein, theterms “has,” “have,” “having,” or the like are intended to be open-endedterms. Further, the phrase “based on” is intended to mean “based atleast partially on” unless explicitly stated otherwise.

As used herein, the terms “communication” and “communicate” may refer tothe reception, receipt, transmission, transfer, provision, and/or thelike of data (e.g., information, signals, messages, instructions,commands, and/or the like). For one unit (e.g., a device, a system, acomponent of a device or system, combinations thereof, and/or the like)to be in communication with another unit means that the one unit is ableto directly or indirectly receive information from and/or send (e.g.,transmit) information to the other unit. This may refer to a direct orindirect connection that is wired and/or wireless in nature.Additionally, two units may be in communication with each other eventhough the information transmitted may be modified, processed, relayed,and/or routed between the first and second unit. For example, a firstunit may be in communication with a second unit even though the firstunit passively receives information and does not actively transmitinformation to the second unit. As another example, a first unit may bein communication with a second unit if at least one intermediary unit(e.g., a third unit located between the first unit and the second unit)processes information received from the first unit and transmits theprocessed information to the second unit. In some non-limiting aspectsor embodiments, a message may refer to a network packet (e.g., a datapacket and/or the like) that includes data.

As used herein, the terms “issuer,” “issuer institution,” “issuer bank,”or “payment device issuer,” may refer to one or more entities thatprovide accounts to individuals (e.g., users, customers, and/or thelike) for conducting payment transactions, such as credit paymenttransactions and/or debit payment transactions. For example, an issuerinstitution may provide an account identifier, such as a primary accountnumber (PAN), to a customer that uniquely identifies one or moreaccounts associated with that customer. In some non-limiting aspects orembodiments, an issuer may be associated with a bank identificationnumber (BIN) that uniquely identifies the issuer institution. As usedherein “issuer system” may refer to one or more computer systemsoperated by or on behalf of an issuer, such as a server executing one ormore software applications. For example, an issuer system may includeone or more authorization servers for authorizing a transaction.

As used herein, the term “account identifier” may refer to one or moretypes of identifiers associated with an account (e.g., a PAN associatedwith an account, a card number associated with an account, a paymentcard number associated with an account, a token associated with anaccount, and/or the like). In some non-limiting aspects or embodiments,an issuer may provide an account identifier (e.g., a PAN, a token,and/or the like) to a user (e.g., an accountholder) that uniquelyidentifies one or more accounts associated with that user. The accountidentifier may be embodied on a payment device (e.g., a physicalinstrument used for conducting payment transactions, such as a paymentcard, a credit card, a debit card, a gift card, and/or the like) and/ormay be electronic information communicated to the user that the user mayuse for electronic payment transactions. In some non-limiting aspects orembodiments, the account identifier may be an original accountidentifier, where the original account identifier was provided to a userat the creation of the account associated with the account identifier.In some non-limiting aspects or embodiments, the account identifier maybe a supplemental account identifier, which may include an accountidentifier that is provided to a user after the original accountidentifier was provided to the user. For example, if the originalaccount identifier is forgotten, stolen, and/or the like, a supplementalaccount identifier may be provided to the user. In some non-limitingaspects or embodiments, an account identifier may be directly orindirectly associated with an issuer institution such that an accountidentifier may be a token that maps to a PAN or other type of accountidentifier. Account identifiers may be alphanumeric, any combination ofcharacters and/or symbols, and/or the like.

As used herein, the term “token” may refer to an account identifier thatis used as a substitute or replacement for another account identifier,such as a PAN. Tokens may be associated with a PAN or other originalaccount identifier in one or more data structures (e.g., one or moredatabases and/or the like) such that they may be used to conduct apayment transaction without directly using the original accountidentifier. In some non-limiting aspects or embodiments, an originalaccount identifier, such as a PAN, may be associated with a plurality oftokens for different individuals or purposes. In some non-limitingaspects or embodiments, tokens may be associated with a PAN or otheraccount identifiers in one or more data structures such that they can beused to conduct a transaction without directly using the PAN or theother account identifiers. In some examples, an account identifier, suchas a PAN, may be associated with a plurality of tokens for differentuses or different purposes.

As used herein, the term “merchant” may refer to one or more entities(e.g., operators of retail businesses) that provide goods and/orservices, and/or access to goods and/or services, to a user (e.g., acustomer, a consumer, and/or the like) based on a transaction, such as apayment transaction. As used herein “merchant system” may refer to oneor more computer systems operated by or on behalf of a merchant, such asa server executing one or more software applications. As used herein,the term “product” may refer to one or more goods and/or servicesoffered by a merchant.

As used herein, a “point-of-sale (POS) device” may refer to one or moredevices, which may be used by a merchant to conduct a transaction (e.g.,a payment transaction) and/or process a transaction. For example, a POSdevice may include one or more client devices. Additionally oralternatively, a POS device may include peripheral devices, cardreaders, scanning devices (e.g., code scanners), Bluetooth®communication receivers, near-field communication (NFC) receivers, radiofrequency identification (RFID) receivers, and/or other contactlesstransceivers or receivers, contact-based receivers, payment terminals,and/or the like. As used herein, a “POS system” may refer to one or moreclient devices and/or peripheral devices used by a merchant to conduct atransaction. For example, a POS system may include one or more POSdevices and/or other like devices that may be used to conduct a paymenttransaction. In some non-limiting aspects or embodiments, a POS system(e.g., a merchant POS system) may include one or more server computersprogrammed or configured to process online payment transactions throughwebpages, mobile applications, and/or the like.

As used herein, the term “transaction service provider” may refer to anentity that receives transaction authorization requests from merchantsor other entities and provides guarantees of payment, in some casesthrough an agreement between the transaction service provider and anissuer institution. For example, a transaction service provider mayinclude a payment network such as Visa®, MasterCard®, American Express®,or any other entity that processes transactions. As used herein“transaction service provider system” may refer to one or more computersystems operated by or on behalf of a transaction service provider, suchas a transaction service provider system executing one or more softwareapplications. A transaction service provider system may include one ormore processors and, in some non-limiting aspects or embodiments, may beoperated by or on behalf of a transaction service provider.

As used herein, the term “acquirer” may refer to an entity licensed bythe transaction service provider and approved by the transaction serviceprovider to originate transactions (e.g., payment transactions)involving a payment device associated with the transaction serviceprovider. As used herein, the term “acquirer system” may also refer toone or more computer systems, computer devices, and/or the like operatedby or on behalf of an acquirer. The transactions the acquirer mayoriginate may include payment transactions (e.g., purchases, originalcredit transactions (OCTs), account funding transactions (AFTs), and/orthe like). In some non-limiting aspects or embodiments, the acquirer maybe authorized by the transaction service provider to assign merchant orservice providers to originate transactions involving a payment deviceassociated with the transaction service provider. The acquirer maycontract with payment facilitators to enable the payment facilitators tosponsor merchants. The acquirer may monitor compliance of the paymentfacilitators in accordance with regulations of the transaction serviceprovider. The acquirer may conduct due diligence of the paymentfacilitators and ensure proper due diligence occurs before signing asponsored merchant. The acquirer may be liable for all transactionservice provider programs that the acquirer operates or sponsors. Theacquirer may be responsible for the acts of the acquirer's paymentfacilitators, merchants that are sponsored by the acquirer's paymentfacilitators, and/or the like. In some non-limiting aspects orembodiments, an acquirer may be a financial institution, such as a bank.

As used herein, the term “payment gateway” may refer to an entity and/ora payment processing system operated by or on behalf of such an entity(e.g., a merchant service provider, a payment service provider, apayment facilitator, a payment facilitator that contracts with anacquirer, a payment aggregator, and/or the like), which provides paymentservices (e.g., transaction service provider payment services, paymentprocessing services, and/or the like) to one or more merchants. Thepayment services may be associated with the use of portable financialdevices managed by a transaction service provider. As used herein, theterm “payment gateway system” may refer to one or more computer systems,computer devices, servers, groups of servers, and/or the like operatedby or on behalf of a payment gateway.

As used herein, the terms “electronic wallet,” “electronic wallet mobileapplication,” and “digital wallet” may refer to one or more electronicdevices including one or more software applications configured tofacilitate and/or conduct transactions (e.g., payment transactions,electronic payment transactions, and/or the like). For example, anelectronic wallet may include a user device (e.g., a mobile device)executing an application program, server-side software, and/or databasesfor maintaining and providing data to be used during a paymenttransaction to the user device. As used herein, the term “electronicwallet provider” may include an entity that provides and/or maintains anelectronic wallet and/or an electronic wallet mobile application for auser (e.g., a customer). Examples of an electronic wallet providerinclude, but are not limited to, Google Wallet™, Android Pay®, ApplePay®, and Samsung Pay®. In some non-limiting examples, a financialinstitution (e.g., an issuer institution) may be an electronic walletprovider. As used herein, the term “electronic wallet provider system”may refer to one or more computer systems, computer devices, servers,groups of servers, and/or the like operated by or on behalf of anelectronic wallet provider.

As used herein, the term “payment device” may refer to a portablefinancial device, an electronic payment device, a payment card (e.g., acredit or debit card), a gift card, a smartcard, smart media, a payrollcard, a healthcare card, a wristband, a machine-readable mediumcontaining account information, a keychain device or fob, an RFIDtransponder, a retailer discount or loyalty card, and/or the like. Thepayment device may include a volatile or a non-volatile memory to storeinformation (e.g., an account identifier, a name of the account holder,and/or the like).

As used herein, the term “computing device” may refer to one or moreelectronic devices that are configured to directly or indirectlycommunicate with or over one or more networks. A computing device may bea mobile or portable computing device, a desktop computer, a server,and/or the like. Furthermore, the term “computer” may refer to anycomputing device that includes the necessary components to receive,process, and output data, and normally includes a display, a processor,a memory, an input device, and a network interface. A “computing system”may include one or more computing devices or computers. An “application”or “application program interface” (API) refers to computer code orother data sorted on a computer-readable medium that may be executed bya processor to facilitate the interaction between software components,such as a client-side front-end and/or server-side back-end forreceiving data from the client. An “interface” refers to a generateddisplay, such as one or more graphical user interfaces (GUIs) with whicha user may interact, either directly or indirectly (e.g., through akeyboard, mouse, touchscreen, etc.). Further, multiple computers, e.g.,servers, or other computerized devices, such as an autonomous vehicleincluding a vehicle computing system, directly or indirectlycommunicating in the network environment may constitute a “system” or a“computing system.”

As used herein, the terms “client” and “client device” may refer to oneor more computing devices, such as processors, storage devices, and/orsimilar computer components, that access a service made available by aserver. In some non-limiting aspects or embodiments, a “client device”may refer to one or more devices that facilitate payment transactions,such as POS devices and/or POS systems used by a merchant. In somenon-limiting aspects or embodiments, a client device may include anelectronic device configured to communicate with one or more networksand/or facilitate payment transactions such as, but not limited to, oneor more desktop computers, one or more portable computers (e.g., tabletcomputers), one or more mobile devices (e.g., cellular phones,smartphones, PDAs, wearable devices, such as watches, glasses, lenses,and/or clothing, and/or the like), and/or other like devices. Moreover,a “client” may also refer to an entity, such as a merchant, that owns,utilizes, and/or operates a client device for facilitating paymenttransactions with a transaction service provider.

As used herein, the term “server” may refer to one or more computingdevices, such as processors, storage devices, and/or similar computercomponents, that communicate with client devices and/or other computingdevices over a network, such as the Internet or private networks and, insome examples, facilitate communication among other servers and/orclient devices.

As used herein, the term “system” may refer to one or more computingdevices or combinations of computing devices such as, but not limitedto, processors, servers, client devices, software applications, and/orother like components. In addition, reference to “a server” or “aprocessor,” as used herein, may refer to a previously-recited serverand/or processor that is recited as performing a previous step orfunction, a different server and/or processor, and/or a combination ofservers and/or processors. For example, as used in the specification andthe claims, a first server and/or a first processor that is recited asperforming a first step or function may refer to the same or differentserver and/or a processor recited as performing a second step orfunction.

Provided are improved systems, methods, and computer program productsfor communicating transaction data between mobile devices. In somenon-limiting aspects or embodiments, a user device and a POS device mayregister with a transaction service provider system to enable thetransaction service provider system to coordinate transactionstherebetween. Registration may include, among other steps, identifying acorrespondence between account data associated with an account (e.g., anaccount of a consumer or a merchant) and device data associated with adevice (e.g., the user device or the POS device). In such an example,the device data may include a unique device identifier (e.g., a phonenumber, media access control (MAC) address, and/or the like) that isassociated with the account data registered to that device by thetransaction service provider system. As a result, where the user deviceor POS device are unable to communicate with one another (e.g., whereone or the other computing device is only able to communicate during atransaction via an SMS messaging service and the other is only able tocommunicate via a data connection), the transaction service providersystem may act as an intermediary and enable communication therebetween.This, in turn, reduces and/or eliminates the need for the regression tolegacy transaction processing techniques (e.g., the use of paper moneyand/or other paper financial instruments that may be more readilymisplaced, misread, and/or the like), and allows for quicker and moresecure access to systems for performing transactions (e.g., atransaction service provider system).

Referring now to FIG. 1 , illustrated is a diagram of a system 100 forcommunicating transaction data between mobile devices according tonon-limiting aspects or embodiments. As illustrated in FIG. 1 , system100 comprises user device 102, point-of-sale (POS) device 104, merchantsystem 106, payment gateway system 108, acquirer system 110, transactionservice provider system 112, issuer system 114, and communicationnetwork 116. User device 102, POS device 104, merchant system 106,payment gateway system 108, acquirer system 110, transaction serviceprovider system 112, and/or issuer system 114 may be in communicationvia communication network 116 and/or one or more wired connections,wireless connections, or a combination of wired and wirelessconnections. Although FIG. 1 shows all of the components of the system100 communicating with communication network 116, it will be appreciatedthat multiple communication networks may be used and that somecomponents may not communicate through the same network.

User device 102 may include a computing device configured to communicatewith POS device 104, merchant system 106, payment gateway system 108,acquirer system 110, transaction service provider system 112, and/orissuer system 114 via communication network 116 and/or other networks.User device 102 may be configured to transmit and/or receive data toand/or from POS device 104 via a short-range wireless communicationconnection (e.g., an NFC communication connection, an RFID communicationconnection, a Bluetooth® communication connection, and/or the like). Insome non-limiting aspects or embodiments, user device 102 may beconfigured to communicate data to and/or from POS device 104, paymentgateway system 108, and/or transaction service provider system 112 via ashort message service (SMS) communication connection (e.g., acommunication connection for transmitting and/or receiving SMS messages)and/or a data connection (e.g., a 2G, 3G, 4G, LTE network, and/or thelike for transmitting and/or receiving data messages such as, withoutlimitation, multimedia messaging service (MMS) messages, and/or otherthe like). In some non-limiting aspects or embodiments, user device 102may be associated with a user (e.g., an individual operating a device).In some non-limiting aspects or embodiments, user device 102 may be apayment device configured to communicate with POS device 104 via ashort-range wireless communication connection.

POS device 104 may include a computing device configured to be incommunication with user device 102, merchant system 106, payment gatewaysystem 108, acquirer system 110, transaction service provider system112, and/or issuer system 114 via communication network 116 and/or othernetworks. POS device 104 may be configured to transmit and/or receivedata to and/or from user device 102 via a short-range wirelesscommunication connection. In some non-limiting aspects or embodiments,POS device 104 may be configured to communicate data to and/or from userdevice 102, merchant system 106, payment gateway system 108, and/ortransaction service provider system 112 via a short message service(SMS) communication connection and/or a data connection. In somenon-limiting aspects or embodiments, POS device 104 may be associatedwith a merchant as described herein.

Merchant system 106 may include one or more computing devices configuredto communicate with user device 102, POS device 104, payment gatewaysystem 108, acquirer system 110, transaction service provider system112, and/or issuer system 114 via communication network 116 and/or othernetworks. For example, merchant system 106 may include one or morecomputing devices configured to transmit and/or receive data to and/orfrom user device 102 and/or POS device 104 via communication network116, such as a server, a group of servers, a client device, a group ofclient devices, and/or other like devices. In some non-limiting aspectsor embodiments, POS device 104 may be part of merchant system 106. Insome non-limiting aspects or embodiments, merchant system 106 may beassociated with a merchant as described herein.

Payment gateway system 108 may include one or more computing devicesconfigured to communicate with user device 102, POS device 104, merchantsystem 106, acquirer system 110, transaction service provider system112, and/or issuer system 114 via communication network 116 and/or othernetworks. For example, payment gateway system 108 may include a server,a group of servers, and/or other like devices. In some non-limitingaspects or embodiments, payment gateway system 108 may be configured totransmit and/or receive data to and/or from user device 102, POS device104, and/or transaction service provider system 112 via an SMScommunication connection and/or a data connection. In some non-limitingaspects or embodiments, payment gateway system 108 may be associatedwith a payment gateway as described herein.

Acquirer system 110 may include one or more computing devices configuredto communicate with user device 102, POS device 104, merchant system106, payment gateway system 108, transaction service provider system112, and/or issuer system 114 via communication network 116 and/or othernetworks. For example, acquirer system 110 may include a server, a groupof servers, and/or other like devices. In some non-limiting aspects orembodiments, acquirer system 110 may be associated with an acquirer asdescribed herein.

Transaction service provider system 112 may include one or morecomputing devices configured to communicate with user device 102, POSdevice 104, merchant system 106, payment gateway system 108, acquirersystem 110, and/or issuer system 114 via communication network 116and/or other networks. For example, transaction service provider system112 may include a server (e.g., a transaction processing server), agroup of servers, and/or other like devices. In some non-limitingaspects or embodiments, transaction service provider system 112 may beassociated with a transaction service provider as described herein. Insome non-limiting aspects or embodiments, transaction service providersystem 112 may be configured to communicate data to and/or from userdevice 102, POS device 104, and/or payment gateway system 108 via an SMScommunication connection and/or a data connection.

Issuer system 114 may include one or more computing devices capable ofbeing in communication with user device 102, POS device 104, merchantsystem 106, payment gateway system 108, acquirer system 110, and/ortransaction service provider system 112 via communication network 116and/or other networks. For example, issuer system 114 may include aserver, a group of servers, and/or other like devices. In somenon-limiting aspects or embodiments, issuer system 114 may be associatedwith an issuer institution that issued a payment account or instrument(e.g., a credit account, a debit account, a credit card, a debit card,etc.) to a user (e.g., a user associated with user device 102, and/orthe like).

Communication network 116 may include one or more wired and/or wirelessnetworks. For example, communication network 116 may include a cellularnetwork (e.g., a long-term evolution (LTE) network, a third generation(3G) network, a fourth-generation (4G) network, a code division multipleaccess (CDMA) network, etc.), a public land mobile network (PLMN), alocal area network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the public switched telephonenetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, and/orthe like, and/or a combination of some or all of these or other types ofnetworks.

The number and arrangement of systems, devices, and networks shown inFIG. 1 are provided as an example. There may be additional systems,devices and/or networks, fewer systems, devices, and/or networks,different systems, devices and/or networks, or differently arrangedsystems, devices, and/or networks than those shown in FIG. 1 .Furthermore, two or more systems or devices shown in FIG. 1 may beimplemented within a single system or a single device, or a singlesystem or a single device shown in FIG. 1 may be implemented asmultiple, distributed systems or devices. Additionally, oralternatively, a set of systems or a set of devices (e.g., one or moresystems, one or more devices) of system 100 may perform one or morefunctions described as being performed by another set of systems oranother set of devices of system 100.

In some non-limiting aspects or embodiments, transaction data associatedwith a transaction may include transaction parameters associated withthe transaction, such as payment transactions initiated and/or conductedwith a computing device (e.g., via an internet browser of a computingdevice), with an electronic wallet application, and/or the like.Non-limiting examples of transaction parameters include: electronicwallet card data associated with a payment device and/or accountidentifier, decision data associated with a decision (e.g., a decisionto approve or deny a transaction authorization request), authorizationdata associated with an authorization response (e.g., an approvedspending limit, an approved transaction value, and/or the like), a PAN,an authorization code (e.g., a PIN, password, etc.), data associatedwith a transaction amount (e.g., an approved limit, a transaction value,etc.), data associated with a transaction date and time, data associatedwith a conversion rate of a currency, data associated with a merchanttype (e.g., goods, grocery, fuel, and/or the like), data associated withan acquiring institution country, data associated with an identifier ofa country associated with the payment device or account, data associatedwith a response code, data associated with a merchant identifier (e.g.,a merchant name, a merchant location, and/or the like), data associatedwith a type of currency corresponding to funds stored in associationwith the PAN, and/or the like.

Referring now to FIG. 2 , illustrated is a diagram of example componentsof device 200. Device 200 may correspond to one or more devices of theuser device 102, one or more devices of POS device 104, one or moredevices of merchant system 106, one or more devices of payment gatewaysystem 108, one or more devices of acquirer system 110, one or moredevices of transaction service provider system 112, one or more devicesof issuer system 114, and/or one or more devices of communicationnetwork 116. In some non-limiting aspects or embodiments, one or moredevices of user device 102, one or more devices of POS device 104, oneor more devices of merchant system 106, one or more devices of paymentgateway system 108, one or more devices of acquirer system 110, one ormore devices of transaction service provider system 112, one or moredevices of issuer system 114, and/or one or more devices ofcommunication network 116 can include at least one device 200 and/or atleast one component of device 200. As shown in FIG. 2 , device 200 mayinclude bus 202, processor 204, memory 206, storage component 208, inputcomponent 210, output component 212, and communication interface 214.

Bus 202 may include a component that permits communication among thecomponents of device 200. In some non-limiting aspects or embodiments,processor 204 may be implemented in hardware, firmware, or a combinationof hardware and software. For example, processor 204 may include aprocessor (e.g., a central processing unit (CPU), a graphics processingunit (GPU), an accelerated processing unit (APU), etc.), amicroprocessor, a digital signal processor (DSP), and/or any processingcomponent (e.g., a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), etc.) that can beprogrammed to perform a function. Memory 206 may include random accessmemory (RAM), read-only memory (ROM), and/or another type of dynamic orstatic storage device (e.g., flash memory, magnetic memory, opticalmemory, etc.) that stores information and/or instructions for use byprocessor 204.

Storage component 208 may store information and/or software related tothe operation and use of device 200. For example, storage component 208may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 210 may include a component that permits device 200 toreceive information, such as via user input (e.g., a touchscreendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, a camera, etc.). Additionally or alternatively, inputcomponent 210 may include a sensor for sensing information (e.g., aglobal positioning system (GPS) component, an accelerometer, agyroscope, an actuator, etc.). Output component 212 may include acomponent that provides output information from device 200 (e.g., adisplay, a speaker, one or more light-emitting diodes (LEDs), etc.).

Communication interface 214 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 200 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 214 may permit device 200to receive information from another device and/or provide information toanother device. For example, communication interface 214 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a WiFi® interface, a cellular network interface,and/or the like.

Device 200 may perform one or more processes described herein. Device200 may perform these processes based on processor 204 executingsoftware instructions stored by a computer-readable medium, such asmemory 206 and/or storage component 208. A computer-readable medium(e.g., a non-transitory computer-readable medium) is defined herein as anon-transitory memory device. A memory device includes memory spacelocated inside of a single physical storage device or memory spacespread across multiple physical storage devices.

Software instructions may be read into memory 206 and/or storagecomponent 208 from another computer-readable medium or from anotherdevice via communication interface 214. When executed, softwareinstructions stored in memory 206 and/or storage component 208 may causeprocessor 204 to perform one or more processes described herein.Additionally or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, embodiments or aspects describedherein are not limited to any specific combination of hardware circuitryand software.

Memory 206 and/or storage component 208 may include data storage or oneor more data structures (e.g., a database, and/or the like). Device 200may be capable of receiving information from, storing information in,communicating information to, or searching information stored in thedata storage or one or more data structures in memory 206 and/or storagecomponent 208. For example, the information may include encryption data,input data, output data, transaction data, account data, or anycombination thereof.

The number and arrangement of components shown in FIG. 2 are provided asan example. In some non-limiting aspects or embodiments, device 200 mayinclude additional components, fewer components, different components,or differently arranged components than those shown in FIG. 2 .Additionally or alternatively, a set of components (e.g., one or morecomponents) of device 200 may perform one or more functions described asbeing performed by another set of components of device 200.

Referring now to FIGS. 3A and 3B, and with continued reference to FIG. 1, illustrated is a flow diagram of a process 300 for communicatingtransaction data between mobile devices. In some non-limiting aspects orembodiments, one or more steps and/or operations associated with process300 may be performed (e.g., completely or partially) by user device 102,POS device 104, and/or transaction service provider system 112 (see FIG.1 ). In some non-limiting aspects or embodiments, one or more of thesteps and/or operations associated with process 300 may be performed(e.g., completely or partially) by another device or group of devicesseparate from, or including, merchant system 106, payment gateway system108, acquirer system 110, and/or issuer system 114. In some non-limitingaspects or embodiments, user device 102 may be used as a POS device asdescribed herein and/or POS device 104 may be used as a user device asdescribed herein.

As described herein, the phrase “push payment” may refer to paymentsduring which a first device (e.g., user device 102, POS device 104,and/or the like) initiates a transaction to transfer funds from anaccount associated with the first device to an account associated with asecond device (e.g., another of user device 102, POS device 104, and/orthe like). Similarly, as described herein, the phrase “pull payment” mayrefer to payments during which a first device (e.g., user device 102,POS device 104, and/or the like) initiates a transaction to transferfunds from an account associated with a second device (e.g., another ofuser device 102, POS device 104, and/or the like) to an accountassociated with the first device. Accordingly, in some non-limitingaspects or embodiments, user device 102 and/or POS device 104 may bothinitiate a push payment or a pull payment.

As shown in FIG. 3A, at step 302, process 300 may include registeringuser device 102 and POS device 104. In some non-limiting aspects orembodiments, transaction service provider system 112 may register userdevice 102 and POS device 104. For example, transaction service providersystem 112 may receive account data associated with an account of a user(e.g., a credit account, a debit account, a currency associated with acredit or debit account, and/or the like) as well as device dataassociated with user device 102, the device data including a uniquedevice identifier (e.g., a phone number, media access control (MAC)address, and/or the like) from user device 102. Similarly, transactionservice provider system 112 may receive account data associated with anaccount of a merchant as well as device data associated with POS device104 from POS device 104. In some non-limiting aspects or embodiments, auser with user device 102 and/or a merchant associated with POS device104 may initiate a telephone call (e.g., using user device 102, POSdevice 104, and/or another computing device capable of initiatingtelephone calls) to transaction service provider system 112 to registeruser device 102 and/or POS device 104. In such examples, transactionservice provider system 112 may receive account data and a unique deviceidentifier from user device 102 and/or POS device 104 based on the userand/or the merchant providing input to user device 102 and/or POS device104.

In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may receive confirmation data associated withconfirmation of a transaction, the confirmation data including a uniqueconfirmation code (e.g., a personal identification number (PIN), apredetermined code (e.g., a card verification code (CVC), and/or thelike), data associated with a Consumer Device Cardholder VerificationMethod (CDCVM)), and/or the like from user device 102 and/or POS device104. In such an example, transaction service provider system 112 maylater compare data received from user device 102 and/or POS device 104during a transaction to the confirmation data received duringregistration of user device 102 and/or POS device 104 to determinewhether the individual operating user device 102 and/or POS device 104is authorized to do so and, by extension, whether or not the transactionis a valid transaction. In some non-limiting aspects or embodiments,transaction service provider system 112 may register an application withuser device 102 and/or POS device 104. For example, transaction serviceprovider system 112 may register the application before or after theapplication is installed on user device 102 and/or POS device 104, andthe application may be used to facilitate communication of data betweenuser device 102 and/or POS device 104 during a transaction as describedherein.

In some non-limiting aspects or embodiments, user device 102 and/or POSdevice 104 may be registered with an issuer system 114. For example, anindividual may provide device data associated with a user device toissuer system 114 (e.g., in person, via a telephone call, and/or thelike). In such an example, issuer system 114 may associate the devicedata associated with the user device with account data associated withthe account of the user. Additionally, or alternatively, an individualmay provide device data associated with a POS device to issuer system114 (e.g., in person, via a telephone call, and/or the like). In such anexample, issuer system 114 may associate the device data associated withthe POS device with account data associated with the account of themerchant. In such examples, the individual registering the device datawith issuer system 114 may also register confirmation data associatedwith confirmation of a transaction with issuer system 114. Additionally,or alternatively, issuer system 114 may associate the device data ofuser device 102 and/or POS device 104 with an account tokencorresponding to the account of the user and/or the account of themerchant, respectively.

In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may store account data associated with an account ofa user in relation to device data associated with user device 102.Additionally, or alternatively, in some non-limiting aspects orembodiments, transaction service provider system 112 may store accountdata associated with an account of a merchant in relation to device dataassociated with POS device 104. As a result of storing the account datain association with the device data for user device 102 and POS device104, transaction service provider system 112 may determine that accountdata associated with the account of the user corresponds to device dataassociated with the user device and/or that the account data associatedwith the account of the merchant corresponds to device data associatedwith POS device 104. In some non-limiting aspects or embodiments,transaction service provider system 112 may transmit the account tokencorresponding to account data of the user to user device 102 and/ortransmit the account token corresponding to account data of the merchantto POS device 104.

As further shown in FIG. 3A, at step 304, process 300 may includereceiving transaction data associated with a transaction. In somenon-limiting aspects or embodiments, transaction service provider system112 may receive transaction data associated with a transaction from userdevice 102 and/or POS device 104. The transaction data associated withthe transaction may comprise: device data associated with the devicetransmitting the transaction data (e.g., user device 102, POS device104, and/or the like), device data associated with a devicecorresponding to an account to or from which funds are to be transferred(e.g., user device 102, POS device 104, and/or the like), and/orparameter data associated with the transaction (e.g., a description ofgoods and/or services purchased, a value of goods and/or servicespurchased, a transaction value, and/or the like). In some non-limitingaspects or embodiments, user device 102 and/or POS device 104 maygenerate transaction data based on receiving input from user device 102and/or POS device 104. In some non-limiting aspects or embodiments, userdevice 102 and/or POS device 104 may generate and transmit an SMSmessage and/or a data message to transaction service provider system112. For example, user device 102 and/or POS device 104 may generate andtransmit an SMS message and/or a data message to transaction serviceprovider system 112, the SMS message and/or the data message includingthe transaction data associated with the transaction. In such anexample, user device 102 and/or POS device 104 may transmit the SMSmessage and/or the data message via an SMS communication connectionand/or a data communication, respectively, to transaction serviceprovider system 112.

In some non-limiting aspects or embodiments, prior to transactionservice provider system 112 receiving transaction data, user device 102and/or POS device 104 may communicate with each other via a short-rangewireless communication connection and/or via communication network 116in order to exchange the transaction data associated with a transaction.For example, user device 102 may establish a short-range wirelesscommunication connection with POS device 104 and, upon establishment,transmit device data associated with user device 102 and/or transactionparameters associated with the transaction to POS device 104. In somenon-limiting aspects or embodiments, user device 102 and/or POS device104 may determine that the other of user device 102 and/or POS device104 is not registered with transaction service provider system 112. Forexample, user device 102 and/or POS device 104 may determine that theother of user device 102 and/or POS device 104 is not registered withtransaction service provider system 112 by transmitting the transactiondata associated with the transaction to transaction service providersystem 112. In such an example, user device 102 and/or POS device 104may receive a message from transaction service provider system 112indicating that user device 102 and/or POS device 104 are not registeredwith transaction service provider system 112.

In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may determine that a device associated with atransaction is not registered with transaction service provider system112 (e.g., that user device 102 and/or POS device 104 are not registeredwith transaction service provider system 112). For example, transactionservice provider system 112 may determine that user device 102 and/orPOS device 104 are not registered with transaction service providersystem 112 and, based on the determination, transmit a messageassociated with the transaction to user device 102 and/or POS device 104to indicate that user device 102 and/or POS device 104 are notregistered with transaction service provider system 112. In somenon-limiting aspects or embodiments, transaction service provider system112 may transmit a message including instructions for how to registerwith transaction service provider system 112 based on determining thatthe device is not registered with transaction service provider system112.

In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may determine that an account corresponds to atransaction. For example, transaction service provider system 112 maydetermine that an account corresponds to a transaction based onreceiving the transaction data associated with the transaction from userdevice 102 or POS device 104. In such an example, transaction serviceprovider system 112 may determine that a transaction authorization limit(e.g., a limit up to which transactions may be processed with funds froman account) applies to the transaction.

As further shown in FIG. 3A, at step 306, process 300 may includedetermining whether sufficient funds are available to satisfy atransaction. In some non-limiting aspects or embodiments, transactionservice provider system 112 may determine whether sufficient funds areavailable to satisfy a transaction based on determining the transactionauthorization limit applies to the transaction. In some non-limitingaspects or embodiments, to determine that the transaction authorizationlimit applies to the transaction, transaction service provider system112 may transmit a pre-authorization request message to issuer system114 requesting a transaction authorization limit for the transactionand, based on transmitting the pre-authorization request message, mayreceive a pre-authorization response message including the transactionauthorization limit. Additionally, or alternatively, transmitting thepre-authorization request message associated with the transaction toissuer system 114 may cause issuer system 114 to transmit apre-authorization response message including an indication as to whatamount of funds are available for the transaction. Where transactionservice provider system 112 determines that sufficient funds areavailable to satisfy a transaction (e.g., that the transactionauthorization limit is greater than a transaction amount; “YES” at step306), a first confirmation message associated with confirmation of thetransaction data may be transmitted. Alternatively, where transactionservice provider system 112 determines that sufficient funds are notavailable to satisfy the transaction (e.g., that the transactionauthorization limit is less than the transaction amount; “NO” at step306), at step 307 transaction service provider system 112 may terminatethe transaction. In some non-limiting aspects or embodiments,transaction service provider system 112 may transmit a messageindicating the transaction was terminated to user device 102 and/or POSdevice 104.

As further shown in FIG. 3A, at step 308, process 300 may includetransmitting a first confirmation message associated with confirmationof transaction data associated with a transaction. In some non-limitingaspects or embodiments, transaction service provider system 112 maytransmit a first confirmation message associated with confirmation of atransaction to confirm that the transaction data is correct. Forexample, transaction service provider system 112 may transmit the firstconfirmation message to user device 102 and/or POS device 104 to confirmthat the transaction data is correct. In such an example, user device102 and/or POS device 104 may display a prompt to cause an individualand/or a merchant to input, via user device 102 and/or POS device 104,respectively, an indication that the transaction data is correct or notcorrect. For example, where transaction service provider system 112receives transaction data associated with a transaction from POS device104 requesting that funds be transferred from an account associated withuser device 102 to an account associated with POS device 104 (e.g., arequest to initiate a pull payment), transaction service provider system112 may generate the first confirmation message associated withconfirmation of the transaction and transmit the first confirmationmessage to user device 102 to confirm the transaction data is correct.Alternatively, for example, where transaction service provider system112 receives transaction data associated with a transaction from userdevice 102 requesting that funds be transferred from the accountassociated with user device 102 to the account associated with POSdevice 104 (e.g., request to initiate a push payment), transactionservice provider system 112 may generate a first confirmation messageassociated with confirmation of the transaction and send the firstconfirmation message to POS device 104 to confirm the transaction datais correct. In some non-limiting aspects or embodiments transactionservice provider system 112 may transmit a first confirmation message asan SMS message and/or a data message to user device 102 and/or POSdevice 104 via an SMS communication connection and/or a datacommunication, respectively.

In some non-limiting aspects or embodiments, a first confirmationresponse message associated with confirmation of a transaction may begenerated. For example, user device 102 and/or POS device 104 maygenerate a first confirmation response message associated withconfirmation of the transaction. In such an example, user device 102and/or POS device 104 may generate the first confirmation responsemessage associated with a transaction based on receiving the indicationthat the transaction data is or is not correct. In such examples, userdevice 102 and/or POS device 104 may transmit the first confirmationresponse message to transaction service provider system 112.

As further shown in FIG. 3A, at step 310, process 300 may includereceiving a first confirmation response message. In some non-limitingaspects or embodiments, transaction service provider system 112 mayreceive a first confirmation response message indicating that thetransaction data is or is not correct and, by extension, is or is notapproved. In such an example, the first confirmation message may betransmitted by user device 102 or POS device 104 to transaction serviceprovider system 112. In some non-limiting aspects or embodiments, userdevice 102 or POS device 104 may transmit the first confirmationresponse message to transaction service provider system 112 as an SMSmessage and/or a data message via an SMS communication connection and/ora data communication, respectively.

As further shown in FIG. 3A, at step 312, process 300 may includedetermining whether a first confirmation response message confirms atransaction. In some non-limiting aspects or embodiments, transactionservice provider system 112 may determine that the first confirmationresponse message confirms a transaction. In some non-limiting aspects orembodiments, transaction service provider system 112 may generate amessage associated with the transaction based on determining that thefirst confirmation response message confirms the transaction. Forexample, transaction service provider system 112 may generate a messageassociated with a transaction indicating that a transaction was approvedor not approved and, after generation, may transmit the message to userdevice 102 and/or POS device 104. As further shown in FIG. 3 , at step313, process 300 may include terminating a transaction. In somenon-limiting aspects or embodiments, transaction service provider system112 may terminate the transaction based on the first confirmationresponse message.

As shown in FIG. 3B, at step 314, process 300 may include determiningwhether a transaction is a high-value transaction. In some non-limitingaspects or embodiments, transaction service provider system 112 maydetermine that a transaction is a high-value transaction (e.g., thetransaction is associated with a transaction amount greater than apredetermined value, and/or the like). For example, in some non-limitingaspects or embodiments, transaction service provider system 112 maydetermine that a transaction is a high-value transaction based on thetransaction parameters included in the transaction data associated withthe transaction. In some non-limiting aspects or embodiments,transaction service provider system 112 may determine that thetransaction is a high-value transaction based on receiving the firstconfirmation response message.

In some non-limiting aspects or embodiments, a second confirmationmessage associated with a transaction may be generated to confirm theidentity of an individual operating a device during the transaction. Forexample, transaction service provider system 112 may generate the secondconfirmation message. In some non-limiting aspects or embodiments,transaction service provider system 112 may generate the secondconfirmation message based on determining that the transaction is ahigh-value transaction. In one such example, POS device 104 may transmittransaction data associated with a transaction requesting funds betransferred from an account associated with a user to an accountassociated with a merchant (e.g., a pull request), and based onreceiving the transaction data, transaction service provider system 112may generate a second confirmation message to be sent to user device 102to confirm the identity of the user operating user device 102. Inanother example, where user device 102 transmits transaction dataassociated with a transaction requesting funds be transferred from anaccount of a user to an account of a merchant (e.g., a push request),transaction service provider system 112 may generate the secondconfirmation message to be sent to user device 102 to confirm theidentity of the individual operating user device 102.

In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may generate the second confirmation message basedon determining that one or more transactions were processed that werenot high-value transactions. For example, transaction service providersystem 112 may determine that one or more transactions processed withina predetermined period of time leading up to the current transactionsatisfies a transaction threshold amount (e.g., an amount oftransactions less than, equal to, or greater than a predeterminedamount). Where transaction service provider system 112 determines thatthe one or more transactions processed within a predetermined period oftime leading up to the current transaction satisfies a transactionthreshold amount, transaction service provider system 112 may generateand transmit the second confirmation message to user device 102 and/orPOS device 104. Where transaction service provider system 112 determinesthat the one or more transactions processed within a predeterminedperiod of time leading up to the current transaction does not satisfy atransaction threshold amount, transaction service provider system 112may not generate the second confirmation message.

In some non-limiting aspects or embodiments, the second confirmationmessage may include a request for data associated with verification ofthe identity of an individual. For example, the second confirmationmessage may include a request for data associated with verification ofthe identity of an individual operating the device that transmitted thetransaction data to transaction service provider system 112.Additionally, or alternatively, the second confirmation message mayinclude a request for data associated with verification of the identityof an individual operating another device involved in the transaction(e.g., where a first device is POS device 104 that is sending a requestfor funds from an account associated with a second device such as userdevice 102, the second confirmation message may include a request fordata associated with the verification of the identity of an individualoperating the another device (e.g., user device 102). In somenon-limiting aspects or embodiments, transmitting the request for dataassociated with verification of the identity of an individual may causethe device that receives the request to generate Consumer DeviceCardholder Verification Method (CDCVM) data and transmit the CDCVM datato transaction service provider system 112. For example, transactionservice provider system 112 may transmitting the request for dataassociated with verification of the identity of an individual operatinguser device 102. In such an example, user device 102 may generate CDCVMdata associated with the identity of the individual operating userdevice 102 (e.g., a fingerprint of the individual, a passcode, and/orthe like). User device 102 may transmit the CDCVM data to transactionservice provider system 112 to verify the identity of the individualoperating user device 102. Similarly, in some non-limiting aspects orembodiments, transaction service provider system 112 may transmittingthe request for data associated with verification of the identity of anindividual operating POS device 104. In such an example, POS device 104may generate CDCVM data associated with the identity of the individualoperating POS device 104. POS device 104 may transmit the CDCVM data totransaction service provider system 112 to verify the identity of theindividual operating POS device 104.

As further shown in FIG. 3B, at step 316, process 300 may includetransmitting a second confirmation message. In some non-limiting aspectsor embodiments, transaction service provider system 112 may transmit asecond confirmation message associated with a transaction to user device102 and/or POS device 104. In some non-limiting aspects or embodiments,user device 102 and/or POS device 104 may receive input and, based onthe input, may generate confirmation data associated with confirmationof the transaction. User device 102 and/or POS device 104 may thengenerate a second confirmation response message associated with thetransaction, and the second confirmation response message may includethe confirmation data associated with confirmation of the transaction.In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may transmit the second confirmation message to userdevice 102 and/or POS device 104 as an SMS message and/or a data messagevia an SMS communication connection and/or a data communication,respectively.

In some non-limiting aspects or embodiments, confirmation dataassociated with confirmation of a transaction may include dataassociated with an identity of an individual operating a device. Forexample, in some non-limiting aspects or embodiments, confirmation datamay include data received as input at user device 102 and/or POS device104 that may be used to identify an individual operating user device 102and/or POS device 104. For a detailed description of verifying theidentity of an individual, reference may be made to PCT PatentApplication No. PCT/GB2019/051011, filed on Apr. 5, 2019, the disclosureof which is hereby incorporated by reference in its entirety.

In some non-limiting aspects or embodiments, transmitting a secondconfirmation message may include initiating a telephone call betweentransaction service provider system 112 and user device 102. Forexample, where user device 102 and/or POS device 104 are configured tocommunicate via an SMS communication connection, transaction serviceprovider system 112 may cause a telephone call to be initiated (e.g., anautomated telephone call) with user device 102 and/or POS device 104 toreceive the confirmation data associated with confirmation of thetransaction. In such an example, an individual operating user device 102may communicate with transaction service provider system 112 to provideconfirmation data associated with confirmation of the transaction totransaction service provider system 112.

As further shown in FIG. 3B, at step 318, process 300 may includereceiving a second confirmation response message associated with atransaction to confirm the transaction. In some non-limiting aspects orembodiments, transaction service provider system 112 may receive asecond confirmation response message from user device 102 or POS device104. In such an example, the second confirmation response message mayinclude the confirmation data associated with confirmation of thetransaction. In some non-limiting aspects or embodiments, user device102 or POS device 104 may transmit the second confirmation responsemessage to transaction service provider system 112 as an SMS messageand/or a data message via an SMS communication connection and/or a datacommunication, respectively.

As further shown in FIG. 3B, at step 320, process 300 may includedetermining whether a second confirmation response message associatedwith a transaction indicates that a transaction is valid. In somenon-limiting aspects or embodiments, transaction service provider system112 may determine whether the second confirmation response indicateswhether the transaction is valid based on comparing the confirmationdata included in the second confirmation response message with theconfirmation data received during registration of the devicetransmitting the second confirmation response message. For example, todetermine that the second confirmation response message is valid,transaction service provider system 112 may compare confirmation dataincluded in the second confirmation response message received from userdevice 102 or POS device 104 with confirmation data received duringregistration of user device 102 and/or POS device 104, respectively.

As further shown in FIG. 3B, at step 321, process 300 may includeterminating a transaction. In some non-limiting aspects or embodiments,transaction service provider system 112 may terminate a transactionbased on determining that the transaction is or is not valid. In such anexample, the determination that the transaction is or is not valid mayinclude comparing the confirmation data included in the secondconfirmation response message to the confirmation data received duringregistration of the device transmitting the second confirmationresponse. Where transaction service provider system 112 determines thatthe transaction is not valid, transaction service provider system 112may terminate the transaction.

In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may re-transmit the second confirmation message touser device 102 and/or POS device 104. For example, transaction serviceprovider system 112 may re-transmit the second confirmation message touser device 102 and/or POS device 104 based on determining that thetransaction is or is not valid based on the second confirmationresponse. In such an example, transaction service provider system 112may receive another second confirmation response message and, based onthe other second confirmation response message, may determine that thetransaction is or is not valid.

As further shown in FIG. 3 , at step 322, process 300 may includeprocessing a transaction. In some non-limiting aspects or embodiments,transaction service provider system 112 may process a transaction. Forexample, transaction service provider system 112 may process thetransaction based on the transaction data associated with a transaction.In such an example, when processing the transaction, transaction serviceprovider system 112 may generate an authorization request messageassociated with authorization of the transaction and, upon generation,transmit the authorization request message to issuer system 114. Issuersystem 114 may, in response to receiving the authorization requestmessage, generate an authorization response message including anindication as to whether the transaction is approved or not approved,and transmit the authorization response message to transaction serviceprovider system 112.

As further shown in FIG. 3 , at step 324, process 300 may includetransmitting a transaction confirmation message indicating whether atransaction was successfully processed or not successfully processed. Insome non-limiting aspects or embodiments, transaction service providersystem 112 may transmit the transaction confirmation message to userdevice 102 and/or POS device 104. For example, transaction serviceprovider system 112 may transmit the transaction confirmation message touser device 102 and/or POS device 104 based on receiving theauthorization response message. The transaction confirmation message mayindicate that a transaction was approved or not approved. In somenon-limiting aspects or embodiments, transaction service provider systemmay transmit the transaction confirmation message to user device 102and/or POS device 104 as an SMS message and/or a data message via an SMScommunication connection and/or a data communication, respectively.

In some non-limiting aspects or embodiments, an electronic receipt maybe transmitted. For example, POS device 104 may transmit an electronicreceipt to user device 102. In such an example, POS device 104 maytransmit the electronic receipt upon successful processing of atransaction. POS device 104 may transmit the electronic receipt to anelectronic wallet on user device 102 and/or to an application executedon user device 102 from an electronic wallet on POS device 104 and/or anapplication executed on POS device 104. In some non-limiting aspects orembodiments, where user device 102 and POS device 104 have anapplication installed thereon to manage communication of transactiondata between mobile devices, the application may be configured toautomatically transmit and/or receive electronic receipts uponsuccessful processing of a transaction.

In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may transmit historical transaction data associatedwith one or more historical transactions to user device 102 and/or POSdevice 104. For example, in some non-limiting aspects or embodiments,user device 102 and/or POS device 104 may receive input indicating arequest for historical transaction data associated with one or morehistorical transactions (e.g., one or more transactions in which userdevice 102 and/or POS device 104 were used to facilitate a transaction).In some non-limiting aspects or embodiments, user device 102 and/or POSdevice 104 may transmit a request to transaction service provider system112 to cause transaction service provider system 112 to transmit thehistorical transaction data to user device 102 and/or POS device 104.Upon receipt, user device 102 and/or POS device 104 may display thehistorical transaction data associated with the one or more transactionson an output component of user device 102 and/or POS device 104. In somenon-limiting aspects or embodiments, a request may include a request forhistorical transaction data associated with one or more historicaltransactions to which the device requesting the historical transactiondata was not a direct party (e.g., one or more POS devices 104 operatingunder the control of a merchant, such as POS devices 104 assigned to oneor more employees of a merchant). In some non-limiting aspects orembodiments, transaction service provider system may transmit thehistorical transaction data associated with the one or more historicaltransactions to user device 102 and/or POS device 104 by including thehistorical transaction data associated with the one or more historicaltransactions in an SMS message and/or a data message transmitted to userdevice 102 and/or POS device 104 via an SMS communication connectionand/or a data communication, respectively.

In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may maintain reports on behalf of POS device 104.For example, transaction service provider system 112 may store dataassociated with one or more transactions that were processed using POSdevice 104. In such an example, transaction service provider system 112may generate one or more reports based on the data associated with theone or more transactions that were processed and transmit the reports toPOS device 104 and/or merchant system 106 to enable a merchant operatingPOS device 104 and/or merchant system 106 to track payments foraccounting purposes, for use as proof of business activity when applyingfor credit, for use when analyzing trends, and/or the like. In somenon-limiting aspects or embodiments, another POS device 104 a maymaintain historical transaction data on behalf of one or more POSdevices 104 and/or may generate one or more reports based on thehistorical transaction data of the one or more POS devices 104.

Referring now to FIG. 4 , illustrated is an implementation 400 ofnon-limiting aspects or embodiments of a process for communicatingtransaction data between mobile devices. As illustrated in FIG. 4 ,implementation 400 includes user device 102, a POS device 104,transaction service provider system 112, and issuer system 114.

As shown by reference number 402 in FIG. 4 , user device 102 mayregister with transaction service provider system 112. Duringregistration, user device 102 may transmit account data associated withan account of a user as well as device data associated with user device102 to transaction service provider system 112. In response, transactionservice provider system 112 may store the account data associated withthe account of the user and the device data associated with user device102 in association with one another (e.g., in a database of transactionservice provider system 112). User device 102 may additionally, oralternatively, transmit confirmation data associated with confirmationof a transaction corresponding to user device 102, and the confirmationdata may include a unique confirmation code. In some non-limitingaspects or embodiments, user device 102 may be used to initiate atelephone call to register with transaction service provider system 112(e.g., via an automated registration system configured to receiveaccount data via audio and/or digital input provided by the user at userdevice 102). In some non-limiting aspects or embodiments, in response toreceiving account data associated with the account of the user anddevice data associated with user device 102, transaction serviceprovider system 112 may generate an account token and transmit theaccount token (e.g., as data or over a telephone call), and the accounttoken may be linked to the account of the user and the device dataassociated with user device 102. In some non-limiting aspects orembodiments, transaction service provider system 112 may transmitconfirmation data associated with confirmation of a transaction to userdevice 102.

As shown by reference number 404 in FIG. 4 , POS device 104 may registerwith transaction service provider system 112. During registration, POSdevice 104 may transmit account data associated with an account of amerchant as well as device data associated with POS device 104 totransaction service provider system 112. In response, transactionservice provider system 112 may store the account data associated withthe account of the merchant and the device data associated with POSdevice 104 in association with one another (e.g., in a database oftransaction service provider system 112). POS device 104 mayadditionally, or alternatively, transmit confirmation data associatedwith confirmation of a transaction corresponding to POS device 104, theconfirmation data including a unique confirmation code. In somenon-limiting aspects or embodiments, POS device 104 may be used toinitiate a telephone call to register with transaction service providersystem 112 (e.g., via an automated registration system configured toreceive account data via audio and/or digital input provided by the userat POS device 104). In some non-limiting aspects or embodiments, inresponse to receiving account data associated with the account of themerchant and device data associated with POS device 104, transactionservice provider system 112 may generate an account token and transmitthe account token (e.g., as data or over a telephone call), and theaccount token may be linked to the account of the merchant and thedevice data associated with POS device 104. In some non-limiting aspectsor embodiments, transaction service provider system 112 may transmitconfirmation data associated with confirmation of a transaction to POSdevice 104.

With continued reference to reference numbers 402 and 404 in FIG. 4 ,transaction service provider system 112 may generate an account tokenfor each device during registration. The account token may be linked tothe account data for each respective device. In some non-limitingaspects or embodiments, transaction service provider system 112 mayprovide confirmation data associated with confirmation of a transactionto user device 102 and/or POS device 104 (e.g., transaction serviceprovider system 112 may generate the confirmation data and transmit theconfirmation data to user device 102 and/or POS device 104).

As shown by reference number 406 in FIG. 4 , transaction serviceprovider system 112 may receive transaction data associated with atransaction from POS device 104. Transaction data may include devicedata associated with user device 102, device data associated with POSdevice 104, and transaction parameters associated with the transactionfrom POS device 104. Transaction service provider system 112 maygenerate a pre-authorization request message associated with thetransaction based on the transaction data associated with thetransaction. In some non-limiting aspects or embodiments, transactionservice provider system 112 may determine whether POS device 104 and/oruser device 102 are registered and, if not registered, transactionservice provider system 112 may transmit a message to POS device 104and/or user device 102 to prompt registration of POS device 104 and/oruser device 102.

As shown by reference number 408 in FIG. 4 , transaction serviceprovider system 112 may transmit a parameter confirmation messageincluding data associated with one or more parameters of the transactionto verify the accuracy of the transaction parameters to POS device 104.For example, transaction service provider system 112 may transmit theparameter confirmation message to POS device 104 based on receiving thetransaction data associated with the transaction. In such an example,the parameter confirmation message may request a parameter confirmationresponse message be returned to transaction service provider system 112indicating whether the transaction parameters associated with thetransaction are accurate.

As shown by reference number 410 in FIG. 4 , transaction serviceprovider system 112 may receive a transaction parameter confirmationresponse message from POS device 104. For example, POS device 104 maygenerate the transaction parameter confirmation response message basedon receiving the transaction parameter confirmation message, thetransaction confirmation response message indicating whether thetransaction parameters associated with the transaction are accurate. Insome non-limiting aspects or embodiments, the transaction parameterconfirmation response message may be generated based on input receivedat POS device 104.

As shown by reference number 412 in FIG. 4 , transaction serviceprovider system 112 may transmit the pre-authorization request messageto issuer system 114. For example, to determine that a transaction ispermissible (e.g., that sufficient funds are available to satisfy atransaction) transaction service provider system 112 may transmit apre-authorization request message to cause issuer system 114 to generatea pre-authorization response message associated with the transaction,the pre-authorization response indicating that sufficient funds are orare not available to satisfy the transaction.

As shown by reference number 414 in FIG. 4 , transaction serviceprovider system 112 receives a pre-authorization response messageassociated with the transaction. The pre-authorization response messagemay indicate that sufficient funds are or are not available to satisfythe transaction. In some non-limiting aspects or embodiments,transaction service provider system 112 may generate a firstconfirmation message associated with the transaction based on thepre-authorization response message. In some non-limiting aspects orembodiments, where the pre-authorization response message indicates thatsufficient funds are not available, transaction service provider system112 may transmit a message to user device 102 and/or POS device 104indicating that insufficient funds are available to satisfy thetransaction.

As shown by reference number 416 in FIG. 4 , transaction serviceprovider system 112 may transmit the first confirmation messageassociated with the transaction to user device 102 to confirmtransaction parameters of the transaction. In some non-limiting aspectsor embodiments, transaction service provider system 112 may transmit thefirst confirmation message via an SMS communication connection or a dataconnection to user device 102. User device 102 may generate a firstconfirmation response based on the first confirmation message. Forexample, user device 102 may generate a display based on the firstconfirmation message to prompt a user to input an indication that thetransaction is accepted or not accepted. User device 102 may receiveinput indicating that the transaction is accepted or not accepted and,based on the input, generate the first confirmation response message.

As shown by reference number 418 in FIG. 4 , transaction serviceprovider system 112 may receive a first confirmation response message.For example, user device 102 may transmit a first confirmation responsemessage based on receiving input indicating acceptance of a transactionby a user at user device 102. In examples where the first confirmationresponse message indicates that the transaction is not accepted,transaction service provider system 112 may transmit a message to POSdevice 104 indicating that the transaction was not accepted.

As shown by reference number 420 in FIG. 4 , transaction serviceprovider system 112 may determine that the transaction is a high-valuetransaction. For example, transaction service provider system 112 maydetermine the transaction is a high-value transaction based ontransaction parameters of the transaction data. Where the transaction isdetermined to be a high-value transaction (e.g., the transaction valueis greater than or equal to a predetermined threshold), transactionservice provider system 112 may generate a second confirmation messageassociated with the transaction. Additionally, or alternatively, wherethe transaction is determined to be a low-value transaction (e.g., thetransaction value is less than or equal to a predetermined threshold),implementation 400 may continue to reference number 426 and transmit anauthorization request message to an issuer system 114.

As shown by reference number 422 in FIG. 4 , transaction serviceprovider system 112 may transmit the second confirmation message to userdevice 102. Transaction service provider system 112 may transmit thesecond confirmation message to user device 102 based on determining thatthe transaction is a high-value transaction. The second confirmationmessage may be configured to cause user device 102 to generate a secondconfirmation response message including confirmation data associatedwith confirmation of the transaction. User device 102 may generateconfirmation data associated with confirmation of the transaction basedon input received at user device 102 (e.g., the input may include aunique confirmation code).

As shown by reference number 424 in FIG. 4 , transaction serviceprovider system 112 may receive a second confirmation response messagefrom user device 102. For example, in some non-limiting aspects orembodiments, transaction service provider system 112 may receive thesecond confirmation response message including confirmation dataassociated with confirmation of the transaction. Transaction serviceprovider system 112 may determine the confirmation data matchesconfirmation data corresponding to the user device 102 received duringregistration of user device 102 with the transaction service providersystem. Transaction service provider system 112 may then generate anauthorization request message associated with the transaction based onthe transaction data and then determine that the confirmation datamatches confirmation data corresponding to the user device 102 receivedduring registration of user device 102.

As shown by reference number 426 in FIG. 4 , transaction serviceprovider system 112 may transmit the authorization request message toissuer system 114. In some non-limiting aspects or embodiments, issuersystem 114 may generate an authorization response message based onreceiving the authorization request message.

As shown by reference number 428 in FIG. 4 , transaction serviceprovider system 112 may receive the authorization response message fromissuer system 114. The authorization response message may indicatewhether the transaction is approved or not approved. In somenon-limiting aspects or embodiments, where the transaction is determinedto be a low-value transaction, an authorization request message may begenerated based on the determination the transaction is a low-valuetransaction, without transmission of a second confirmation message andreceipt of a second confirmation response by the transaction serviceprovider system 112. In some non-limiting aspects or embodiments,transaction service provider system 112 may transmit a message to userdevice 102 and/or POS device 104 indicating that the transaction wasapproved or not approved.

Referring now to FIGS. 5A and 5B, illustrated is an implementation 500of non-limiting aspects or embodiments of a process for communicatingtransaction data between mobile devices. As illustrated in FIGS. 5A and5B, implementation 500 includes user device 102, POS device 104,transaction service provider system 112, and issuer system 114.

As shown by reference number 502 in FIG. 5A, user device 102 mayregister with transaction service provider system 112. Duringregistration, user device 102 may transmit account data associated withan account of a user as well as device data associated with user device102 to transaction service provider system 112. In response, transactionservice provider system 112 may store the account data associated withthe account of the user and the device data associated with user device102 in association with one another (e.g., in a database of transactionservice provider system 112). User device 102 may additionally, oralternatively, transmit confirmation data associated with confirmationof a transaction corresponding to user device 102, the confirmation dataincluding a unique confirmation code. In some non-limiting aspects orembodiments, user device 102 may be used to make a telephone call toregister with transaction service provider system 112. In somenon-limiting aspects or embodiments, in response to receiving accountdata associated with the account of the user and device data associatedwith user device 102, transaction service provider system 112 maygenerate an account token and transmit the account token (e.g., as dataor over a telephone call), the account token linked to the account ofthe user and the device data associated with user device 102. In somenon-limiting aspects or embodiments, transaction service provider system112 may transmit confirmation data associated with confirmation of atransaction to user device 102.

As shown by reference number 504 in FIG. 5A, POS device 104 may registerwith transaction service provider system 112. During registration, POSdevice 104 may transmit account data associated with an account of amerchant as well as device data associated with POS device 104 totransaction service provider system 112. In response, transactionservice provider system 112 may store the account data associated withthe account of the merchant and the device data associated with POSdevice 104 in association with one another (e.g., in a database oftransaction service provider system 112). POS device 104 mayadditionally, or alternatively, transmit confirmation data associatedwith confirmation of a transaction corresponding to POS device 104, theconfirmation data including a unique confirmation code. In somenon-limiting aspects or embodiments, POS device 104 may be used to makea telephone call to register with transaction service provider system112. In some non-limiting aspects or embodiments, in response toreceiving account data associated with the account of the merchant anddevice data associated with POS device 104, transaction service providersystem 112 may generate an account token and transmit the account token(e.g., as data or over a telephone call), and the account token may belinked to the account of the merchant and the device data associatedwith POS device 104. In some non-limiting aspects or embodiments,transaction service provider system 112 may transmit confirmation dataassociated with confirmation of a transaction to POS device 104.

As shown by reference number 506 in FIG. 5A, user device 102 maytransmit transaction data associated with a transaction to transactionservice provider system 112. For example, user device 102 may transmittransaction data including device data associated with POS device 104,device data associated with user device 102, and transaction parametersassociated with the transaction to transaction service provider system112 to initiate a transaction. Transaction service provider system 112may generate a pre-authorization request associated with the transactionbased on receiving the transaction data from user device 102.

As shown by reference number 508 in FIG. 5A, transaction serviceprovider system 112 may transmit a first confirmation message to userdevice 102 to confirm the transaction (e.g., a push payment thatincludes the withdrawal of funds from a user account corresponding touser device 102 for transfer to a merchant account corresponding to POSdevice 104). User device 102 may generate a first confirmation responsemessage based on the first confirmation message, the first confirmationresponse message including data associated with an indication as towhether the transaction is approved or not approved. For example, insome non-limiting aspects or embodiments, user device 102 may generate adisplay based on the first confirmation message to cause a user to inputan indication that the transaction is approved or not approved. Userdevice 102 may receive input and, based on the input, generate a firstconfirmation response message including data indicating that thetransaction is approved or not approved.

As shown by reference number 510 in FIG. 5A, transaction serviceprovider system 112 receives a first confirmation response message. Forexample, user device 102 may transmit the first confirmation responsebased on receiving input indicating acceptance or non-acceptance of atransaction by a user at user device 102.

As shown by reference number 512 in FIG. 5A, transaction serviceprovider system 112 may transmit the pre-authorization request messageto issuer system 114. For example, to determine whether a transactioncan be processed (e.g., whether sufficient funds are or are notavailable in an account drawn from to satisfy a transaction) transactionservice provider system 112 may transmit a pre-authorization requestmessage to cause issuer system 114 to generate a pre-authorizationresponse message indicating that sufficient funds are or are notavailable from the account associated with user device 102 to satisfythe transaction.

As shown by reference number 514 in FIG. 5A, transaction serviceprovider system 112 receives a pre-authorization response messageincluding data indicating that the transaction is approved or notapproved. Where the pre-authorization response message indicates thatinsufficient funds are available to satisfy the transaction, thetransaction may be terminated. In some non-limiting aspects orembodiments, where the pre-authorization response message indicates thatinsufficient funds are available to satisfy the transaction, transactionservice provider system 112 may send a message to user device 102, themessage including data indicating that insufficient funds are availableto satisfy the transaction.

As shown by reference number 516 in FIG. 5A, transaction serviceprovider system 112 may determine that the transaction is a high-valuetransaction. For example, transaction service provider system 112 maydetermine the transaction is a high-value transaction based ontransaction parameters of the transaction data. Additionally, oralternatively, where the transaction is determined to be a low-valuetransaction, implementation 500 may continue to reference number 522 andtransmit an authorization request message to an issuer system 114.

As shown by reference number 518 in FIG. 5B, transaction serviceprovider system 112 may transmit a second confirmation message to userdevice 102. Transaction service provider system 112 may transmit thesecond confirmation message to user device 102 to cause user device 102to generate a second confirmation response message includingconfirmation data associated with confirmation of the transaction. Userdevice 102 may generate confirmation data associated with confirmationof the transaction based on input received at user device 102 (e.g., theinput of a unique confirmation code).

As shown by reference number 520 in FIG. 5B, transaction serviceprovider system 112 may receive a second confirmation response messagefrom user device 102. For example, transaction service provider system112 may receive a second confirmation response message includingconfirmation data associated with confirmation of the transaction fromuser device 102. Transaction service provider system 112 may determinethat the confirmation data matches confirmation data corresponding tothe user device 102 received during registration of user device 102 withthe transaction service provider system. The transaction serviceprovider system 112 may generate an authorization request messageassociated with the transaction based on the transaction data associatedwith the transaction and the determination that the second confirmationresponse message includes confirmation data that matches theconfirmation data corresponding to the user device 102 received duringregistration of user device 102.

As shown by reference number 522 in FIG. 5B, transaction serviceprovider system 112 may transmit an authorization request message toissuer system 114, the authorization request message based ontransaction data associated with the transaction. In some non-limitingaspects or embodiments, issuer system 114 may generate an authorizationresponse message based on the authorization request.

As shown by reference number 524 in FIG. 5B, transaction serviceprovider system 112 may receive an authorization response message fromissuer system 114. For example, transaction service provider system 112may receive the authorization response message from issuer system 114,the authorization response indicating that the transaction is acceptedor not accepted. In some non-limiting aspects or embodiments, where thetransaction is determined to be a low-value transaction, anauthorization request message may be generated based on thedetermination the transaction is a low-value transaction, without thetransmission of a second confirmation message and reception of a secondconfirmation response message by the transaction service provider system112.

As shown by reference number 526 in FIG. 5B, a payment confirmationmessage may be transmitted to user device 102. For example, transactionservice provider system 112 may transmit the payment confirmation touser device 102, the payment confirmation message including dataassociated with an indication as to whether the transaction was approvedor not approved. User device 102 may display an indication that thetransaction was processed and approved or not approved based onreceiving the payment confirmation message.

As shown by reference number 528 in FIG. 5B, transaction serviceprovider system 112 may transmit a payment confirmation message to POSdevice 104. For example, transaction service provider system 112 maytransmit the payment confirmation to POS device 104, the paymentconfirmation message including data associated with an indication as towhether the transaction was approved or not approved. POS device 104 maydisplay an indication that the transaction was processed and approved ornot approved based on receiving the payment confirmation message.

Referring now to FIGS. 6A and 6B, illustrated is an implementation 600of non-limiting aspects or embodiments of a process for communicatingtransaction data between mobile devices. As illustrated in FIGS. 6A and6B, implementation 600 includes user device 102, POS device 104,transaction service provider system 112, and issuer system 114.

As shown by reference number 602 in FIG. 6A, user device 102 mayregister with transaction service provider system 112. Duringregistration, user device 102 may transmit account data associated withan account of a user as well as device data associated with user device102 to transaction service provider system 112. In response, transactionservice provider system 112 may store the account data associated withthe account of the user and the device data associated with user device102 in association with one another (e.g., in a database of transactionservice provider system 112). User device 102 may additionally, oralternatively, transmit confirmation data associated with confirmationof a transaction corresponding to user device 102, the confirmation dataincluding a unique confirmation code. In some non-limiting aspects orembodiments, user device 102 may be used to make a telephone call toregister with transaction service provider system 112. In somenon-limiting aspects or embodiments, in response to receiving accountdata associated with the account of the user and device data associatedwith user device 102, transaction service provider system 112 maygenerate an account token and transmit the account token (e.g., as dataor over a telephone call), and the account token may be linked to theaccount of the user and the device data associated with user device 102.In some non-limiting aspects or embodiments, transaction serviceprovider system 112 may transmit confirmation data associated withconfirmation of a transaction to user device 102.

As shown by reference number 604 in FIG. 6A, POS device 104 may registerwith transaction service provider system 112. During registration, POSdevice 104 may transmit account data associated with an account of amerchant as well as device data associated with POS device 104 totransaction service provider system 112. In response, transactionservice provider system 112 may store the account data associated withthe account of the merchant and the device data associated with POSdevice 104 in association with one another (e.g., in a database oftransaction service provider system 112). POS device 104 mayadditionally, or alternatively, transmit confirmation data associatedwith confirmation of a transaction corresponding to POS device 104, theconfirmation data including a unique confirmation code. In somenon-limiting aspects or embodiments, POS device 104 may be used toinitiate a telephone call to register with transaction service providersystem 112. In some non-limiting aspects or embodiments, in response toreceiving account data associated with the account of the merchant anddevice data associated with POS device 104, transaction service providersystem 112 may generate an account token and transmit the account token(e.g., as data or over a telephone call), the account token linked tothe account of the merchant and the device data associated with POSdevice 104. In some non-limiting aspects or embodiments, transactionservice provider system 112 may transmit confirmation data associatedwith confirmation of a transaction to POS device 104.

As shown by reference number 606 in FIG. 6A, user device 102 maytransmit transaction data associated with a transaction to POS device104 either via a short-range wireless communication connection, an SMScommunication connection, and/or a data connection. Transaction data mayinclude device data associated with user device 102 and/or transactionparameters associated with the transaction. In some non-limiting aspectsor embodiments, user device 102 and/or POS device 104 may determine thatuser device 102 and/or POS device 104 are not configured to exchangetransaction data and, upon such a determination, may generate a displayindicating that the devices are not configured to exchange transactiondata (e.g., that the devices have installed therein incompatibleelectronic wallet applications and/or the like).

As shown by reference number 608 in FIG. 6A, POS device 104 may transmitthe transaction data to transaction service provider system 112. Forexample, POS device 104 may transmit transaction data including devicedata associated with user device 102, device data associated with POSdevice 104, and/or transaction parameters associated with thetransaction. Transaction service provider system 112 may generate afirst confirmation message based on receiving the transaction data.

As shown by reference number 610 in FIG. 6A, transaction serviceprovider system 112 may transmit a first confirmation message to userdevice 102. User device 102 may generate a display based on the firstconfirmation message and, based on the display, may receive inputindicating that the transaction is confirmed or not confirmed. Userdevice 102 may generate a first confirmation response message indicatingwhether the transaction is confirmed or not confirmed based on receivingthe input.

As shown by reference number 612 in FIG. 6A, user device 102 maytransmit a first confirmation response message to transaction serviceprovider system 112. Transaction service provider system 112 maydetermine whether the transaction is confirmed or not confirmed based onthe first confirmation response message. Transaction service providersystem 112 may generate a pre-authorization request message based on thefirst confirmation response message and/or the transaction data.

As shown by reference number 614 in FIG. 6A, transaction serviceprovider system 112 may transmit a pre-authorization request message toissuer system 114. Issuer system 114 may generate a pre-authorizationresponse message based on the pre-authorization request message.

As shown by reference number 616 in FIG. 6A, transaction serviceprovider system 112 may receive a pre-authorization response messagefrom issuer system 114.

As shown by reference number 618 in FIG. 6A, transaction serviceprovider system 112 may determine whether the transaction is ahigh-value transaction. For example, where the transaction is determinedto be a high-value transaction, transaction service provider system 112may generate and transmit a second confirmation message. Additionally,or alternatively, where the transaction is determined to be a low-valuetransaction, the transaction service provider system 112 may process thetransaction (see reference numbers 624-630 of FIG. 6B).

As shown by reference number 620 in FIG. 6B, transaction serviceprovider system 112 may transmit a second confirmation message to userdevice 102. User device 102 may generate a display and receive an inputbased on generating the display, the input including confirmation dataassociated with confirmation of the transaction.

As shown by reference number 622 in FIG. 6B, transaction serviceprovider system 112 may receive a second confirmation response from userdevice 102. Transaction service provider system 112 may determinewhether the transaction is valid or not valid based on the secondconfirmation response message and, in response to determining that it isvalid, may generate an authorization request message.

As shown by reference number 624 in FIG. 6B, transaction serviceprovider system 112 may transmit an authorization request message toissuer system 114. Issuer system 114 may determine whether thetransaction is authorized and, based on the determination, may generatean authorization response message.

As shown by reference number 626 in FIG. 6B, transaction serviceprovider system 112 may receive an authorization response message fromissuer system 114.

As shown by reference number 628 in FIG. 6B, transaction serviceprovider system 112 may transmit a payment confirmation message to userdevice 102, the payment confirmation message including data associatedwith an indication as to whether the transaction was approved or notapproved.

As shown by reference number 630 in FIG. 6B, transaction serviceprovider system 112 may transmit a payment confirmation message to POSdevice 104, the payment confirmation message including data associatedwith an indication as to whether the transaction was approved or notapproved.

Although examples have been described in detail for the purpose ofillustration based on what is currently considered to be the mostpractical and preferred aspects or embodiments, it is to be understoodthat such detail is solely for that purpose and that the principlesdescribed by the present disclosure are not limited to the disclosedaspects or embodiments, but, on the contrary, is intended to covermodifications and equivalent arrangements that are within the spirit andscope of the appended claims. For example, it is to be understood thatthe present disclosure contemplates that, to the extent possible, one ormore features of any embodiment can be combined with one or morefeatures of any other embodiment.

What is claimed is:
 1. A computer-implemented method for communicatingtransaction data between mobile devices, the computer-implemented methodcomprising: receiving, with at least one processor from a point-of-sale(POS) device, account data associated with a merchant account and devicedata associated with the POS device, wherein the device data associatedwith the POS device comprises short message service (SMS) device dataassociated with the POS device; registering, with at least oneprocessor, the account data associated with the merchant account ascorresponding to the SMS device data associated with the POS device inan application hosted by a transaction service provider system;receiving, with at least one processor from a user device, account dataassociated with a user account and device data associated with the userdevice, wherein the device data associated with the user devicecomprises SMS device data associated with the user device; registering,with at least one processor, the account data associated with the useraccount as corresponding to the SMS device data associated with the userdevice in the application hosted by the transaction service providersystem; receiving, with at least one processor via an SMS communicationconnection, transaction data associated with a transaction from the POSdevice, comprising: the SMS device data associated with the POS device,the SMS device data associated with the user device, and parameter dataassociated with the transaction, the transaction initiated by the POSdevice, the parameter data comprising a transaction value, verifying,with at least one processor, that the POS device and the user device areregistered in the application hosted by the transaction service providersystem in response to receiving the SMS device data associated with thePOS device and the SMS device data associated with the user device;transmitting, with at least one processor, a transaction parameterconfirmation message to the POS device based on receiving thetransaction data; receiving, with at least one processor from the POSdevice, a transaction parameter confirmation response message;transmitting, with at least one processor, a pre-authorization requestmessage to an issuer server in response to receiving the transactionparameter confirmation response message from the POS device; receiving,with at least one processor from the issuer server, a pre- authorizationresponse message comprising an indication based on an account balance ofthe user account being greater than the transaction value; based onreceiving the pre-authorization response message comprising theindication transmitting, with at least one processor, a firstconfirmation message associated with the transaction, via an SMScommunication connection, to the user device to confirm the transaction;receiving, with at least one processor from the user device, a firstconfirmation response message via the SMS communication connection; andbased on receiving the first confirmation response message, processing,with at least one processor, the transaction data.
 2. Thecomputer-implemented method according to claim 1, further comprising:based on determining that a transaction authorization limit is greaterthan an authorization limit threshold, transmitting, with at least oneprocessor, a second confirmation message associated with the transactionto the user device; and based on receiving a second confirmationresponse message associated with the transaction, confirming, with atleast one processor and prior to processing the transaction data, that asecond confirmation response is valid.
 3. The computer-implementedmethod according to claim 1, wherein registering account data associatedwith the account as corresponding to the SMS device data associated withthe user device further comprises: registering, with at least oneprocessor, confirmation data associated with confirmation of thetransaction, the confirmation data corresponding to the SMS device dataassociated with the user device.
 4. The computer-implemented methodaccording to claim 2, further comprising: determining, with at least oneprocessor, that the second confirmation response message indicates thatthe transaction is valid based on a comparison of the secondconfirmation response message to confirmation data received duringregistration of the account data associated with the user accountcorresponding to the SMS device data associated with the user device. 5.The computer-implemented method according to claim 1, wherein verifyingthe POS device and the user device are registered further comprises:determining, with at least one processor, that the SMS device dataassociated with the POS device corresponds to the account dataassociated with the merchant account; and determining, with at least oneprocessor, that the SMS device data associated with the user devicecorresponds to the account data associated with the user account.
 6. Thecomputer-implemented method according to claim 1, wherein verifying thePOS device and the user device are registered further comprises: basedon determining that at least one of the POS device and the user deviceare not registered, transmitting, with at least one processor, a messageassociated with the transaction to the at least one of the POS deviceand the user device indicating that the at least one of the POS deviceand the user device are not registered.
 7. A system for communicatingtransaction data between mobile devices, the system comprising: at leastone processor programmed or configured to: receive, from a point-of-sale(POS) device, account data associated with a merchant account and devicedata associated with the POS device, wherein the device data associatedwith the POS device comprises short message service (SMS) device dataassociated with the POS device; register the account data associatedwith the merchant account as corresponding to the SMS device dataassociated with the POS device in an application hosted by a transactionservice provider system; receive, from a user device, account dataassociated with a user account and device data associated with the userdevice, wherein the device data associated with the user devicecomprises SMS device data associated with the user device: register theaccount data associated with the user account as corresponding to theSMS device data associated with the user device in the applicationhosted by the transaction service provider system; receive, via an SMScommunication connection, transaction data associated with a transactionfrom the POS device, comprising: the SMS device data associated with thePOS device, the SMS device data associated with the user device, andparameter data associated with the transaction, the transactioninitiated by the POS device, the parameter data comprising a transactionvalue, verify that the POS device and the user device are registered inthe application hosted by the transaction service provider system inresponse to receiving the SMS device data associated with the POS deviceand the SMS device data associated with the user device; transmit atransaction parameter confirmation message to the POS device based onreceiving the transaction data; receive, from the POS device, atransaction parameter confirmation response message; transmit apre-authorization request message to an issuer server in response toreceiving the transaction parameter confirmation response message fromthe POS device; receive, from the issuer server, a pre-authorizationresponse message comprising an indication based on an account balance ofthe user account being greater than the transaction value; based onreceiving the pre-authorization response message comprising theindication, transmit a first confirmation message associated with thetransaction, via an SMS communication connection, to the user device toconfirm the transaction; receive, from the user device, a firstconfirmation response message via the SMS communication connection; andbased on receiving the first confirmation response message, process thetransaction data.
 8. The system according to claim 7, wherein the atleast one processor is further programmed or configured to: based ondetermining that a transaction authorization limit is greater than anauthorization limit threshold, transmit a second confirmation messageassociated with the transaction to the user device; and based onreceiving a second confirmation response message associated with thetransaction, confirm, prior to processing the transaction data, that asecond confirmation response is valid.
 9. The system according to claim7, wherein, when registering account data associated with the useraccount as corresponding to the SMS device data associated with the userdevice, the at least one processor is programmed or configured to:register confirmation data associated with confirmation of thetransaction, the confirmation data corresponding to the SMS device dataassociated with the user device.
 10. The system according to claim 8,wherein the at least one processor is further programmed or configuredto: determine that the second confirmation response message indicatesthat the transaction is valid based on a comparison of the secondconfirmation response message to confirmation data received duringregistration of the account data associated with the user accountcorresponding to the SMS device data associated with the user device.11. The system according to claim 7, wherein, when verifying that thePOS device and the user device are registered, the at least oneprocessor is programmed or configured to: determine that the SMS devicedata associated with the POS device corresponds to the account dataassociated with the merchant account; and determine that the SMS devicedata associated with the user device corresponds to the account dataassociated with the user account.
 12. The system according to claim 7,wherein, when verifying that the POS device and the user device areregistered, the at least one processor is programmed or configured to:based on determining that at least one of the POS device and the userdevice are not registered, transmit a message associated with thetransaction to the at least one of the POS device and the user deviceindicating that the at least one of the POS device and the user deviceare not registered.
 13. A computer-program product for communicatingtransaction data between mobile devices, the computer program productcomprising at least one non-transitory computer-readable mediumcomprising one or more instructions that, when executed by at least oneprocessor, cause the at least one processor to: receive, from apoint-of-sale (POS) device, account data associated with a merchantaccount and device data associated with the POS device, wherein thedevice data associated with the POS device comprises short messageservice (SMS) device data associated with the POS device; register theaccount data associated with the merchant account as corresponding tothe SMS device data associated with the POS device in an applicationhosted by a transaction service provider system; receive, from a userdevice, account data associated with a user account and device dataassociated with the user device, wherein the device data associated withthe user device comprises SMS device data associated with the userdevice; register the account data associated with the user account ascorresponding to the SMS device data associated with the user device inthe application hosted by the transaction service provider system;receive, via an SMS communication connection, transaction dataassociated with a transaction from the POS device, comprising: the SMSdevice data associated with the POS device, the SMS device dataassociated with the user device, and parameter data associated with thetransaction, the transaction initiated by the POS device, the parameterdata comprising a transaction value, verify that the POS device and theuser device are registered in the application hosted by the transactionservice provider system in response to receiving the SMS device dataassociated with the POS device and the SMS device data associated withthe user device; transmit a transaction parameter confirmation messageto the POS device based on receiving the transaction data; receive, fromthe POS device, a transaction parameter confirmation response message;transmit a pre-authorization request message to an issuer server inresponse to receiving the transaction parameter confirmation responsemessage from the POS device; receive, from the issuer server, apre-authorization response message comprising an indication based on anaccount balance of the user account being greater than the transactionvalue; based on receiving the pre-authorization response messagecomprising the indication, transmit a first confirmation messageassociated with the transaction, via an SMS communication connection, tothe user device to confirm the transaction; receive, from the userdevice, a first confirmation response message via the SMS communicationconnection; and based on receiving a the first confirmation responsemessage, process the transaction data.
 14. The computer program productaccording to claim 13, wherein the one or more instructions furthercause the at least one processor to: based on determining that atransaction authorization limit is greater than an authorization limitthreshold, transmit a second confirmation message associated with thetransaction to the user device; and based on receiving the secondconfirmation response message associated with the transaction, confirm,prior to processing the transaction data, that a second confirmationresponse is valid.
 15. The computer program product according to claim13, wherein the one or more instructions that cause the at least oneprocessor to register account data associated with an account ascorresponding to the SMS device data associated with the user devicecause the at least one processor to: register confirmation dataassociated with confirmation of the transaction, the confirmation datacorresponding to the SMS device data associated with the user device.16. The computer program product according to claim 14, wherein the oneor more instructions further cause the at least one processor to:determine that the second confirmation response message indicates thatthe transaction is valid based on a comparison of the secondconfirmation response message to confirmation data received duringregistration of the account data associated with the accountcorresponding to the SMS device data associated with the user device.